Error in the plugin:descriptor goal

[hermod.opstvedt]

Hi

When running mvn install on various projects I am now getting:
[INFO] [plugin:descriptor]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO] Extractor for language: java found 1 mojo descriptors.
[INFO] Applying extractor for language: bsh
[INFO] Extractor for language: bsh found 0 mojo descriptors.
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] org.apache.maven.plugin.descriptor.Parameter.getImplementation()Ljava/lan
g/String;
[INFO] 
[INFO] Trace
java.lang.NoSuchMethodError: org.apache.maven.plugin.descriptor.Parameter.getImp
lementation()Ljava/lang/String;
at org.apache.maven.tools.plugin.generator.PluginDescriptorGenerator.pro
cessMojoDescriptor(PluginDescriptorGenerator.java:338)
at org.apache.maven.tools.plugin.generator.PluginDescriptorGenerator.exe
cute(PluginDescriptorGenerator.java:87)
at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(Abstract
GeneratorMojo.java:103)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
.

Is there an error in the plugin or is there another library that is out of date?

Hermod


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB NOR cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email. 

This email message has been virus checked by the anti virus programs used
in the DnB NOR Group.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


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

Re: notice about recent assembly plugin snapshot

[Brett Porter]

was this behaviour only in previous snapshots of the current release,
or was it that way in the previous release?

On 31/08/06, John Casey <[EMAIL PROTECTED]> wrote:

Hi everyone,

I just wanted to send a quick note to let you know that I've made some
modifications to the way the assembly plugin functions. These changes are
likely to break your assemblies if you're using the
moduleSets/moduleSet/sources element.

The sources element used to be derived from fileSet, in that you could
provide directory, outputDirectory, includes, excludes, etc. directly on
that element. This sources element would determine how source-files from
module children and grandchildren of your project were included. In some
recent work, I've noticed that it's sometimes useful to be more flexible
with module source inclusion. So, I've made the sources element a
free-standing class, no longer derived from the fileSet.

So, to replicate this:


  

  src
  
**/*.bak
**/*~
  

  


you'd need to change it to the following:



  

  

  src
  
**/*.bak
**/*~
  

  

  


I've deployed this new snapshot for people to try out, but changes like this
and other new features of the moduleSet section are not documented yet. I'm
planning to flesh out the documentation for these new parts soon, and call a
release, as I think we're nearing a good cut-off point, before beginning a
new round of features. I just wanted to make sure I didn't leave people
saying, "WTF? This used to work!" tonight.

-john





--
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/

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

Re: Can't release due to SNAPSHOT dependencies

[Doug Douglass]

mvn help:effective-pom should help you get a pom that can be tweaked for
corporate deployment.

Doug

On 8/30/06, Wayne Fay <[EMAIL PROTECTED]> wrote:


I would guess that another pom somewhere else (or possibly even not in
the source code you've got) is introducing this people.apache.org url.

Two choices to chase this down...
1. Look in the pom for maven-idea-plugin. Find the parent reference.
Go to that pom, check its parent. Rinse and repeat until eventually
you find all the relevant poms and one of them probably has the
people.apache.org reference.

2. Grep the Maven source code you've downloaded for
"people.apache.org". Then grep your Maven install directory and your
Maven local cache for this same url. I imagine you'll find it.

Sorry I can't be more specific ("oh you need to edit file
x/y/z/pom.xml"). Perhaps someone else can comment on this specific
plugin??

Wayne

On 8/30/06, Dave Hoffer <[EMAIL PROTECTED]> wrote:
> Here is a current example of the problem I have with the deploy goal.  I
> am trying to deploy a current build of the maven-idea-plugin.
>
> - I have checked out the entire maven source.
> - At .\plugins\maven-idea-plugin I can install fine (but need to deploy
> to our repo.
> - I then edit .\plugins\maven-idea-plugin\pom.xml to be version
> 2.0.1-beta20060830.
> - I then search for the pom file that has the distributionManagement
> repository/snapshotRepository entries.  It looks like the only pom that
> has this is .\pom\asf\pom.xml.  I change these to use our local repo.
>
> When I run mvn deploy I get:
>
>
> [INFO] [jar:jar]
> [INFO] Building jar:
> C:\svn\maven2\plugins\maven-idea-plugin\target\maven-idea-p
> lugin-2.0.1-beta20060830.jar
> [INFO] [plugin:addPluginArtifactMetadata]
> [INFO] [install:install]
> [INFO] Installing
> C:\svn\maven2\plugins\maven-idea-plugin\target\maven-idea-plug
> in-2.0.1-beta20060830.jar to C:\Documents and
> Settings\DaveHoffer\.m2\repository
> \org\apache\maven\plugins\maven-idea-plugin\2.0.1-beta20060830\maven-ide
> a-plugin
> -2.0.1-beta20060830.jar
> [INFO] [plugin:updateRegistry]
> [INFO] [deploy:deploy]
> The authenticity of host 'people.apache.org' can't be established.
> DSA key fingerprint is 79:7c:cb:6a:44:47:b2:ef:5c:66:28:d7:40:0d:b1:f9.
> Are you sure you want to continue connecting? (yes/no): no
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Error deploying artifact: Authentication failed: Cannot connect.
> Reason:
> reject HostKey: people.apache.org
>
>
> Why does it want to connect to 'people.apache.org'?
>
> -dh
>
>
>
> -Original Message-
> From: Dave Hoffer [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 30, 2006 8:49 PM
> To: Maven Users List
> Subject: RE: Can't release due to SNAPSHOT dependencies
>
> Wayne,
>
> ...just to clarify.
>
> In order to deploy to my corporate repo I would have to edit the pom
> files to deploy to my corporate repo instead of the real one.  With some
> large projects, i.e. maven plugins I have had trouble making the
> necessary pom changes (lots of parent poms) to get the deploy to work.
>
> However, if this is the suggested approach I will try it again.
>
> -dh
>
>
> -Original Message-
> From: Douglas Ferguson [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 30, 2006 12:21 PM
> To: users
> Subject: RE: Can't release due to SNAPSHOT dependencies
>
> Thanks.
>
> That makes a lot of sense...
>
> -Original Message-
> From: Wayne Fay [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 30, 2006 10:12 AM
> To: Maven Users List
> Subject: Re: Can't release due to SNAPSHOT dependencies
>
> We've talked about this before on the list, and this is the generally
> suggested approach...
>
> Download the code for the plugin(s) from SVN/CVS.
> Increment the version number to a fixed/released number, build,
> install locally and deploy to your corporate repo (if you have one) or
> provide it to your coworkers some other way.
> Update your pom to reflect the new plugin version number.
>
> Generally I would suggest you incorporate a timestamp into the build
> number ie maven-war-plugin 2.1.20060830 just to keep it clear that
> this is not necessarily a real release.
>
> Make sure you understand the artifact version system before picking a
> build number, or else you could easily end up with a situation where
> the "official" plugin releases a new version but your internal plugin
> is still considered "newer" ie if a plugin last released 2.0.5 and is
> currently releasing 2.1-SNAPSHOT, you might want to tag yours as 2.0.6
> or 2.0.5.1 -- if you tag it as 2.1, then you won't get the "real" 2.1
> release when it is final. (Of course, if the plugin release 2.0.6 then
> you'll get a collision there too...)
>
> Wayne
>
> On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
> > I am using some snapshot plugins so it won't let me release.
> >

Re: pruning or limiting snapshots

[jim stafford]

Barrie,

Thanks! uniqueVersion is what I needed.
http://maven.apache.org/ref/current/maven-model/maven.html#class_snapshotRepository

I do have separate release and snapshot repositories. Although I am 
still trying to sort out my use of SNAPSHOTS versus versions, in this 
case they are the result of nightly or other milestone builds. People 
will see the artifact and the source assembly in the snapshot repository 
before they see it in SVN.


I would feel quite sloppy if I saw 100s of versions out there knowing 
that 99.9% of the time the latest version is what is needed. I can see 
the point where other projects want to lock into a stable environment 
(just happens not to be true in my case). For that, I could see them 
turing off snapshot updates.


thanks again,
jim

Barrie Treloar wrote:


On 8/31/06, jim stafford <[EMAIL PROTECTED]> wrote:


Is there any way to limit the number of SNAPSHOTs that accumulate in the
SNAPSHOT repository using only Maven?

I realize I can use shell script pruning tools and cron to help reduce
the clutter, but I was wondering if there was a way of getting the
deploy plugin to do the work. It looks like each deploy adds another
version of the SNAPSHOT without replacing the previous versions.



You want those snapshots kept so that you can reproduce your builds.
But given that snapshots are development builds you could clean them
up, but I'm not sure it is worth that much effort. Disk space is cheap
right?

You should have two repositories, one for release artifacts and one
for snapshot artifacts.
So theoretically, if you have just released your application you could
just delete the snapshot repository, but if more than one project is
using that repository deleting would be a bad thing (tm).

The other problem you might run into if you delete selected files is
that the metadata would refer to things that no longer exist.

Alternatively, if you just want to keep one snapshot you can use the
uniqueVersion, see
http://www.nabble.com/forum/ViewPost.jtp?post=5971992&framed=y

-
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: pruning or limiting snapshots

[Barrie Treloar]

On 8/31/06, jim stafford <[EMAIL PROTECTED]> wrote:

Is there any way to limit the number of SNAPSHOTs that accumulate in the
SNAPSHOT repository using only Maven?

I realize I can use shell script pruning tools and cron to help reduce
the clutter, but I was wondering if there was a way of getting the
deploy plugin to do the work. It looks like each deploy adds another
version of the SNAPSHOT without replacing the previous versions.


You want those snapshots kept so that you can reproduce your builds.
But given that snapshots are development builds you could clean them
up, but I'm not sure it is worth that much effort. Disk space is cheap
right?

You should have two repositories, one for release artifacts and one
for snapshot artifacts.
So theoretically, if you have just released your application you could
just delete the snapshot repository, but if more than one project is
using that repository deleting would be a bad thing (tm).

The other problem you might run into if you delete selected files is
that the metadata would refer to things that no longer exist.

Alternatively, if you just want to keep one snapshot you can use the
uniqueVersion, see
http://www.nabble.com/forum/ViewPost.jtp?post=5971992&framed=y

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

Re: [M2] Creating archetypes

[Takashi Nishigaya]

Hi ccadete,

try my bash completion script:

http://blogs.sun.com/nishigaya/entry/bash_completion_for_maven_2

it will complemet plugin parameters as well as well-known plugin
goals.
the above entry is written in japanse, sorry. But you can easily
find the link for the actual bash completion script.

Thanks,
Takashi Nishigaya

ccadete wrote:



Yes, it was that, now it is working :) thanks.

ccadete




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

Re: Multipart question regarding releasing with an assembly and integration tests.

[Wendy Smoak]

On 8/30/06, Todd Nine <[EMAIL PROTECTED]> wrote:


2. I have a project that has both unit tests and integration tests.  The
unit tests use mock objects and obviously execute automatically when test is
performed.  How do I specify the tests that need to run for integration
testing?  Also note that I will need to start Jboss in the
pre-integration-test phase and shut it down in the post-integration-test
phase.  I'm trying the codehaus mojo plug in, but it doesn't quite work as
expected, I may end up using cargo.  Does anyone have a strong opinion of
cargo and any relevant experience?


Yes. Cargo is great. :)

Maven doesn't handle having both unit _and_ integration tests in the
same module very well yet.  If you have the option, move the
integration tests to a separate module.  There is an example of this
in the 'Better Builds with Maven' book:
http://www.mergere.com/m2book_download.jsp

If not, and you have to keep the tests together, here's a simple example:
 
http://svn.apache.org/repos/asf/shale/framework/trunk/shale-apps/shale-blank/pom.xml

You have to play around with the includes/excludes so the integration
tests don't run during 'mvn test'.  Then you reverse the pattern when
the "itest" profile is active.  You can also see the configuration for
Cargo, which gets used in the CargoTestSetup class to start and stop
the container.

Please come join us on the mailing lists if you have more questions about Cargo:
 http://cargo.codehaus.org/Mailing+Lists

--
Wendy

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

Re: Can't release due to SNAPSHOT dependencies

[Wayne Fay]

I would guess that another pom somewhere else (or possibly even not in
the source code you've got) is introducing this people.apache.org url.

Two choices to chase this down...
1. Look in the pom for maven-idea-plugin. Find the parent reference.
Go to that pom, check its parent. Rinse and repeat until eventually
you find all the relevant poms and one of them probably has the
people.apache.org reference.

2. Grep the Maven source code you've downloaded for
"people.apache.org". Then grep your Maven install directory and your
Maven local cache for this same url. I imagine you'll find it.

Sorry I can't be more specific ("oh you need to edit file
x/y/z/pom.xml"). Perhaps someone else can comment on this specific
plugin??

Wayne

On 8/30/06, Dave Hoffer <[EMAIL PROTECTED]> wrote:

Here is a current example of the problem I have with the deploy goal.  I
am trying to deploy a current build of the maven-idea-plugin.

- I have checked out the entire maven source.
- At .\plugins\maven-idea-plugin I can install fine (but need to deploy
to our repo.
- I then edit .\plugins\maven-idea-plugin\pom.xml to be version
2.0.1-beta20060830.
- I then search for the pom file that has the distributionManagement
repository/snapshotRepository entries.  It looks like the only pom that
has this is .\pom\asf\pom.xml.  I change these to use our local repo.

When I run mvn deploy I get:


[INFO] [jar:jar]
[INFO] Building jar:
C:\svn\maven2\plugins\maven-idea-plugin\target\maven-idea-p
lugin-2.0.1-beta20060830.jar
[INFO] [plugin:addPluginArtifactMetadata]
[INFO] [install:install]
[INFO] Installing
C:\svn\maven2\plugins\maven-idea-plugin\target\maven-idea-plug
in-2.0.1-beta20060830.jar to C:\Documents and
Settings\DaveHoffer\.m2\repository
\org\apache\maven\plugins\maven-idea-plugin\2.0.1-beta20060830\maven-ide
a-plugin
-2.0.1-beta20060830.jar
[INFO] [plugin:updateRegistry]
[INFO] [deploy:deploy]
The authenticity of host 'people.apache.org' can't be established.
DSA key fingerprint is 79:7c:cb:6a:44:47:b2:ef:5c:66:28:d7:40:0d:b1:f9.
Are you sure you want to continue connecting? (yes/no): no
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error deploying artifact: Authentication failed: Cannot connect.
Reason:
reject HostKey: people.apache.org


Why does it want to connect to 'people.apache.org'?

-dh



-Original Message-
From: Dave Hoffer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 8:49 PM
To: Maven Users List
Subject: RE: Can't release due to SNAPSHOT dependencies

Wayne,

...just to clarify.

In order to deploy to my corporate repo I would have to edit the pom
files to deploy to my corporate repo instead of the real one.  With some
large projects, i.e. maven plugins I have had trouble making the
necessary pom changes (lots of parent poms) to get the deploy to work.

However, if this is the suggested approach I will try it again.

-dh


-Original Message-
From: Douglas Ferguson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 12:21 PM
To: users
Subject: RE: Can't release due to SNAPSHOT dependencies

Thanks.

That makes a lot of sense...

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 10:12 AM
To: Maven Users List
Subject: Re: Can't release due to SNAPSHOT dependencies

We've talked about this before on the list, and this is the generally
suggested approach...

Download the code for the plugin(s) from SVN/CVS.
Increment the version number to a fixed/released number, build,
install locally and deploy to your corporate repo (if you have one) or
provide it to your coworkers some other way.
Update your pom to reflect the new plugin version number.

Generally I would suggest you incorporate a timestamp into the build
number ie maven-war-plugin 2.1.20060830 just to keep it clear that
this is not necessarily a real release.

Make sure you understand the artifact version system before picking a
build number, or else you could easily end up with a situation where
the "official" plugin releases a new version but your internal plugin
is still considered "newer" ie if a plugin last released 2.0.5 and is
currently releasing 2.1-SNAPSHOT, you might want to tag yours as 2.0.6
or 2.0.5.1 -- if you tag it as 2.1, then you won't get the "real" 2.1
release when it is final. (Of course, if the plugin release 2.0.6 then
you'll get a collision there too...)

Wayne

On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
> I am using some snapshot plugins so it won't let me release.
>
>
>
> I can understand not wanting to release because of a dependency on
code
> or library snapshots, but for I don't have any issues with releasing
> something that is dependent on a snapshot of a tool, like cargo.
>
>
>
> Is there a way around this?
>
>
>
>

-
To unsubscribe, e-

pruning or limiting snapshots

[jim stafford]

Is there any way to limit the number of SNAPSHOTs that accumulate in the 
SNAPSHOT repository using only Maven?


I realize I can use shell script pruning tools and cron to help reduce 
the clutter, but I was wondering if there was a way of getting the 
deploy plugin to do the work. It looks like each deploy adds another 
version of the SNAPSHOT without replacing the previous versions.


thanks,
jim

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

Re: Turning off All Repositories

[Wayne Fay]

You can "turn off" ibiblio by setting up an alternative repo as a
central in your settings.xml file.

Wayne

On 8/30/06, Dave Hoffer <[EMAIL PROTECTED]> wrote:

Humm...not sure what you mean.  Maven does just use those in the pom
plus ibiblio.  I don't think you can shut off ibiblio.

-dh

-Original Message-
From: Ole Ersoy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 10:25 PM
To: users@maven.apache.org
Subject: Turning off All Repositories

Hi,

Does anyone know how to turn off all repositories, so
that Maven is only allowed to use repositories
specified in the POM?

Thanks,
- Ole

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


-
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: Can't release due to SNAPSHOT dependencies

[Barrie Treloar]

On 8/31/06, Dave Hoffer <[EMAIL PROTECTED]> wrote:

Why does it want to connect to 'people.apache.org'?


If you check the pom files you will find that people.apache.org has
been defined as a repository, probably to get access to the SNAPSHOT
of another plugin.

http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins will
walk you through the steps.

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

Re: Can't release due to SNAPSHOT dependencies

[Barrie Treloar]

On 8/31/06, Wayne Fay <[EMAIL PROTECTED]> wrote:

Download the code for the plugin(s) from SVN/CVS.
Increment the version number to a fixed/released number, build,
install locally and deploy to your corporate repo (if you have one) or
provide it to your coworkers some other way.
Update your pom to reflect the new plugin version number.

Generally I would suggest you incorporate a timestamp into the build
number ie maven-war-plugin 2.1.20060830 just to keep it clear that
this is not necessarily a real release.

Make sure you understand the artifact version system before picking a
build number, or else you could easily end up with a situation where
the "official" plugin releases a new version but your internal plugin
is still considered "newer" ie if a plugin last released 2.0.5 and is
currently releasing 2.1-SNAPSHOT, you might want to tag yours as 2.0.6
or 2.0.5.1 -- if you tag it as 2.1, then you won't get the "real" 2.1
release when it is final. (Of course, if the plugin release 2.0.6 then
you'll get a collision there too...)


I wrote this up here
http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins

It's what I used to release our team's code which needed snaphot
plugins + patches.

The wiki docs assume the next release is going to match the -SNAPSHOT
version being developed and that a younger release won't sneak in for
some critical reason.

Of course, the docs do warn you that when a release is made that you
need to double check it includes any patches that you manually
applied, as you may need to re-apply them.

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

Re: Multipart question regarding releasing with an assembly and integration tests.

[Barrie Treloar]

1. I have a project that is simply a testing utility for our admins to test
their message queue setups.  I have the assembler plug in create a zip file
that contains all the jars and the class path for the executable jar.  Is it
possible for me to automatically run the assembly and upload the created zip
during release:perform?


Check out the nabble archives there are a couple posts I have replied
to that provide examples of this.  One in particular is
http://www.nabble.com/forum/ViewPost.jtp?post=6069982&framed=y

You can bind the assembly plugin so that it will run during the
package phase and this will automatically attach the *-bin.zip file
created in the repository during deploy and releases.

This means your admins can "self-serve" the test utilities by web
browsing your internal maven repository and downloading the correct
versions.


2. I have a project that has both unit tests and integration tests.  The
unit tests use mock objects and obviously execute automatically when test is
performed.  How do I specify the tests that need to run for integration
testing?  Also note that I will need to start Jboss in the
pre-integration-test phase and shut it down in the post-integration-test
phase.  I'm trying the codehaus mojo plug in, but it doesn't quite work as
expected, I may end up using cargo.  Does anyone have a strong opinion of
cargo and any relevant experience?


I haven't done this step yet so can't help with anything but theory.

I do know that you need to separate out your integration tests or else
they will get matched by surefire and will be run as unit tests (which
isn't what you want).
Your choices are move the tests to src/integration-test/java or move
them to another project.

You can then bind the plugins you need to the correct phases to run
your integration tests.

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

RE: pom files not validating

[Douglas Ferguson]

Yeah.. I already have a 3rd party branch. I just didn't realize that it would 
barf at me cuz the pom was skeletal. Some of this stuff doesn't even have a 
pom, i.e. some weird library from a partner, etc.

-Original Message-
From: Mykel Alvis [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 4:21 PM
To: Maven Users List
Subject: Re: pom files not validating

My $0.02:

I used to do this, but I've since decided that it's worth the time to take
the generated POM from the maven deploy, go back to the projects (where I'm
able to), and update the POM to make it into a "real" POM instead of a
skeletal one.

I ended up with a large number of dependencies in projects that were
essentially transitive, but had to be included at the base level because
they were transitive to 3rd party dependencies, not to our actual project.
I wish people who packaged deployments to central would do this more often.

I also suggest making sure that you separate your internal repository from
your [internally-deployed EXTERNAL/3rd party] repository.  It's made a lot
of difference since I could make one of my ongoing tasks into "look for
public repositories for the 3rd party jars", such as when java-dev-net made
the javax libs available.



On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
>
> I deployed them with mvn deploy:deploy-file.
> I had previously used mvn install:install-file and then copied them from
> there to the internal repository, but there where no poms. So I then ran mvn
> deploy:deploy-file.
>
> I let maven generate the poms.
>
> -Original Message-
> From: Yann Le Du [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 30, 2006 1:51 PM
> To: Maven Users List
> Subject: Re: pom files not validating
>
> How did you deploy your 3rd party library ? With mvn install:install-file
> ?
> Then, did you use the generatePom option or did you write the POM yourself
> ?
>
> - Yann
>
> 2006/8/30, Douglas Ferguson <[EMAIL PROTECTED]>:
> >
> > I have some 3rd party library dependencies that aren't in central so I
> > deployed them to our internal repository.
> >
> >
> >
> > Whenever I build a project that depends on one of these libraries I get
> > the following message.
> >
> >
> >
> > What can I do to get stop this?
> >
> >
> >
> > [WARNING] POM for 'uk.co.demon.windsong:crypt:pom:0.0.1:provided' is
> > invalid. It will be ignored for
> >
> > artifact resolution. Reason: Failed to validate POM
> >
> >
> >
> > I tried deleting the pom but then it tries to go out and find it. I'd
> > like to speed up the build by have the poms available.
> >
> >
> >
> > D-
> >
> >
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
I'm just an unfrozen caveman software developer.  I don't understand your
strange, "modern" ways.


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

RE: Turning off All Repositories

[Dave Hoffer]

Humm...not sure what you mean.  Maven does just use those in the pom
plus ibiblio.  I don't think you can shut off ibiblio.

-dh

-Original Message-
From: Ole Ersoy [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 10:25 PM
To: users@maven.apache.org
Subject: Turning off All Repositories

Hi,

Does anyone know how to turn off all repositories, so
that Maven is only allowed to use repositories
specified in the POM?

Thanks,
- Ole

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


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

RE: Can't release due to SNAPSHOT dependencies

[Dave Hoffer]

Problem with another option to deploy as well...

I notice that I can use the deploy:deploy-file to deploy an artifact
with an existing pom.  I think this would accomplish the same as the
deploy goal below.

Here is the syntax I used:  mvn deploy:deploy-file
-DpomFile= \
-Dfile= \
-DrepositoryId= \
-Durl=

When I execute this, the jar gets deployed just fine.  However the pom
gets deleted from my current directory and I get an error stating that
Error installing metadata: Error rewriting POM

Then it says (The system cannot find the file specified)

Well it deleted the file...how can I fix this?

I have problems with both deploy options

-dh

P.S. My maven version is 2.0.4.  Do I need to be running a snapshot
version that has this fixed?  Is it an issue that I am deploying
something newer than I am?



-Original Message-
From: Dave Hoffer [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 9:47 PM
To: Maven Users List
Subject: RE: Can't release due to SNAPSHOT dependencies

Here is a current example of the problem I have with the deploy goal.  I
am trying to deploy a current build of the maven-idea-plugin.

- I have checked out the entire maven source.
- At .\plugins\maven-idea-plugin I can install fine (but need to deploy
to our repo.
- I then edit .\plugins\maven-idea-plugin\pom.xml to be version
2.0.1-beta20060830.
- I then search for the pom file that has the distributionManagement
repository/snapshotRepository entries.  It looks like the only pom that
has this is .\pom\asf\pom.xml.  I change these to use our local repo.

When I run mvn deploy I get:


[INFO] [jar:jar]
[INFO] Building jar:
C:\svn\maven2\plugins\maven-idea-plugin\target\maven-idea-p
lugin-2.0.1-beta20060830.jar
[INFO] [plugin:addPluginArtifactMetadata]
[INFO] [install:install]
[INFO] Installing
C:\svn\maven2\plugins\maven-idea-plugin\target\maven-idea-plug
in-2.0.1-beta20060830.jar to C:\Documents and
Settings\DaveHoffer\.m2\repository
\org\apache\maven\plugins\maven-idea-plugin\2.0.1-beta20060830\maven-ide
a-plugin
-2.0.1-beta20060830.jar
[INFO] [plugin:updateRegistry]
[INFO] [deploy:deploy]
The authenticity of host 'people.apache.org' can't be established.
DSA key fingerprint is 79:7c:cb:6a:44:47:b2:ef:5c:66:28:d7:40:0d:b1:f9.
Are you sure you want to continue connecting? (yes/no): no
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error deploying artifact: Authentication failed: Cannot connect.
Reason:
reject HostKey: people.apache.org


Why does it want to connect to 'people.apache.org'?

-dh



-Original Message-
From: Dave Hoffer [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 8:49 PM
To: Maven Users List
Subject: RE: Can't release due to SNAPSHOT dependencies

Wayne,

...just to clarify.

In order to deploy to my corporate repo I would have to edit the pom
files to deploy to my corporate repo instead of the real one.  With some
large projects, i.e. maven plugins I have had trouble making the
necessary pom changes (lots of parent poms) to get the deploy to work.

However, if this is the suggested approach I will try it again.

-dh


-Original Message-
From: Douglas Ferguson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 12:21 PM
To: users
Subject: RE: Can't release due to SNAPSHOT dependencies

Thanks.

That makes a lot of sense...

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 10:12 AM
To: Maven Users List
Subject: Re: Can't release due to SNAPSHOT dependencies

We've talked about this before on the list, and this is the generally
suggested approach...

Download the code for the plugin(s) from SVN/CVS.
Increment the version number to a fixed/released number, build,
install locally and deploy to your corporate repo (if you have one) or
provide it to your coworkers some other way.
Update your pom to reflect the new plugin version number.

Generally I would suggest you incorporate a timestamp into the build
number ie maven-war-plugin 2.1.20060830 just to keep it clear that
this is not necessarily a real release.

Make sure you understand the artifact version system before picking a
build number, or else you could easily end up with a situation where
the "official" plugin releases a new version but your internal plugin
is still considered "newer" ie if a plugin last released 2.0.5 and is
currently releasing 2.1-SNAPSHOT, you might want to tag yours as 2.0.6
or 2.0.5.1 -- if you tag it as 2.1, then you won't get the "real" 2.1
release when it is final. (Of course, if the plugin release 2.0.6 then
you'll get a collision there too...)

Wayne

On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
> I am using some snapshot plugins so it won't let me release.
>
>
>
> I can understand not wanting to release because of a dependency on
code
> or library snapshots,

Turning off All Repositories

[Ole Ersoy]

Hi,

Does anyone know how to turn off all repositories, so
that Maven is only allowed to use repositories
specified in the POM?

Thanks,
- Ole

__
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: Spring Framework Dependencies

[Jared Bunting]

I have attached a zip containing poms and checksums for 1.2.8 to the ticket
you mention.  What else do I need to do to get these uploaded to ibiblio?

Thanks,
Jared

On 8/30/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:


any questions about spring and their poms must be asked there, or you
provide the poms to be uploaded to ibiblio.

On 8/30/06, Pin Ngee Koh <[EMAIL PROTECTED]> wrote:
> Do I download repository from http://www.ibiblio.org/maven2 and unzip
> spring-pom-1.2.8.zip over it?
> Is there a reason why we are not keeping http://www.ibiblio.org/maven2
>  update to date?
>
> On 8/30/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > see http://opensource.atlassian.com/projects/spring/browse/SPR-1484
> >
> > On 8/30/06, Pin Ngee Koh <[EMAIL PROTECTED]> wrote:
> > > I have many artifacts which dependent on spring.
> > > What's the best way to declare dependency on Spring - specifically
1.2.8?
> > > I can think of the following ways:
> > >
> > > (1) Declare a parent pom with the right dependencies to spring-core,
> > > spring-orm, ...etc. And have each project pom inherit it
> > >
> > > Issue: some pom does not have the right transtive dependency. E.g.
> > > http://www.ibiblio.org/maven2/org/springframework/spring-core/1.2.8/
> > > does not have dependency declared for commons-logging.
> > >
> > > (2) Declare dependency on org.springframework:spring:1.2.8. But it
> > > does not include the right transitive dependencies
> > >
> > > Somehow, http://www.ibiblio.org/maven2 does not seems to have the
> > > complete dependencies defined. Am I missing something here?
> > >
> > >  /
> > > c=-oo
> > >   \  o
> > >
> > >
-
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> > -- The Princess Bride
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
>  /
> c=-oo
>   \  o
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
 -- The Princess Bride

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

RE: Can't release due to SNAPSHOT dependencies

[Dave Hoffer]

Here is a current example of the problem I have with the deploy goal.  I
am trying to deploy a current build of the maven-idea-plugin.

- I have checked out the entire maven source.
- At .\plugins\maven-idea-plugin I can install fine (but need to deploy
to our repo.
- I then edit .\plugins\maven-idea-plugin\pom.xml to be version
2.0.1-beta20060830.
- I then search for the pom file that has the distributionManagement
repository/snapshotRepository entries.  It looks like the only pom that
has this is .\pom\asf\pom.xml.  I change these to use our local repo.

When I run mvn deploy I get:


[INFO] [jar:jar]
[INFO] Building jar:
C:\svn\maven2\plugins\maven-idea-plugin\target\maven-idea-p
lugin-2.0.1-beta20060830.jar
[INFO] [plugin:addPluginArtifactMetadata]
[INFO] [install:install]
[INFO] Installing
C:\svn\maven2\plugins\maven-idea-plugin\target\maven-idea-plug
in-2.0.1-beta20060830.jar to C:\Documents and
Settings\DaveHoffer\.m2\repository
\org\apache\maven\plugins\maven-idea-plugin\2.0.1-beta20060830\maven-ide
a-plugin
-2.0.1-beta20060830.jar
[INFO] [plugin:updateRegistry]
[INFO] [deploy:deploy]
The authenticity of host 'people.apache.org' can't be established.
DSA key fingerprint is 79:7c:cb:6a:44:47:b2:ef:5c:66:28:d7:40:0d:b1:f9.
Are you sure you want to continue connecting? (yes/no): no
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error deploying artifact: Authentication failed: Cannot connect.
Reason:
reject HostKey: people.apache.org


Why does it want to connect to 'people.apache.org'?

-dh



-Original Message-
From: Dave Hoffer [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 8:49 PM
To: Maven Users List
Subject: RE: Can't release due to SNAPSHOT dependencies

Wayne,

...just to clarify.

In order to deploy to my corporate repo I would have to edit the pom
files to deploy to my corporate repo instead of the real one.  With some
large projects, i.e. maven plugins I have had trouble making the
necessary pom changes (lots of parent poms) to get the deploy to work.

However, if this is the suggested approach I will try it again.

-dh


-Original Message-
From: Douglas Ferguson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 12:21 PM
To: users
Subject: RE: Can't release due to SNAPSHOT dependencies

Thanks.

That makes a lot of sense...

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 10:12 AM
To: Maven Users List
Subject: Re: Can't release due to SNAPSHOT dependencies

We've talked about this before on the list, and this is the generally
suggested approach...

Download the code for the plugin(s) from SVN/CVS.
Increment the version number to a fixed/released number, build,
install locally and deploy to your corporate repo (if you have one) or
provide it to your coworkers some other way.
Update your pom to reflect the new plugin version number.

Generally I would suggest you incorporate a timestamp into the build
number ie maven-war-plugin 2.1.20060830 just to keep it clear that
this is not necessarily a real release.

Make sure you understand the artifact version system before picking a
build number, or else you could easily end up with a situation where
the "official" plugin releases a new version but your internal plugin
is still considered "newer" ie if a plugin last released 2.0.5 and is
currently releasing 2.1-SNAPSHOT, you might want to tag yours as 2.0.6
or 2.0.5.1 -- if you tag it as 2.1, then you won't get the "real" 2.1
release when it is final. (Of course, if the plugin release 2.0.6 then
you'll get a collision there too...)

Wayne

On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
> I am using some snapshot plugins so it won't let me release.
>
>
>
> I can understand not wanting to release because of a dependency on
code
> or library snapshots, but for I don't have any issues with releasing
> something that is dependent on a snapshot of a tool, like cargo.
>
>
>
> Is there a way around this?
>
>
>
>

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

Multipart question regarding releasing with an assembly and integration tests.

[Todd Nine]

Hi all,
 I have a couple of questions that don't seem to be documented (at least
not that I could find).  Any help would be greatly appreciated.

1. I have a project that is simply a testing utility for our admins to test
their message queue setups.  I have the assembler plug in create a zip file
that contains all the jars and the class path for the executable jar.  Is it
possible for me to automatically run the assembly and upload the created zip
during release:perform?

2. I have a project that has both unit tests and integration tests.  The
unit tests use mock objects and obviously execute automatically when test is
performed.  How do I specify the tests that need to run for integration
testing?  Also note that I will need to start Jboss in the
pre-integration-test phase and shut it down in the post-integration-test
phase.  I'm trying the codehaus mojo plug in, but it doesn't quite work as
expected, I may end up using cargo.  Does anyone have a strong opinion of
cargo and any relevant experience?


Thanks,
Todd

RE: Can't release due to SNAPSHOT dependencies

[Dave Hoffer]

Wayne,

...just to clarify.

In order to deploy to my corporate repo I would have to edit the pom
files to deploy to my corporate repo instead of the real one.  With some
large projects, i.e. maven plugins I have had trouble making the
necessary pom changes (lots of parent poms) to get the deploy to work.

However, if this is the suggested approach I will try it again.

-dh


-Original Message-
From: Douglas Ferguson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 12:21 PM
To: users
Subject: RE: Can't release due to SNAPSHOT dependencies

Thanks.

That makes a lot of sense...

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 10:12 AM
To: Maven Users List
Subject: Re: Can't release due to SNAPSHOT dependencies

We've talked about this before on the list, and this is the generally
suggested approach...

Download the code for the plugin(s) from SVN/CVS.
Increment the version number to a fixed/released number, build,
install locally and deploy to your corporate repo (if you have one) or
provide it to your coworkers some other way.
Update your pom to reflect the new plugin version number.

Generally I would suggest you incorporate a timestamp into the build
number ie maven-war-plugin 2.1.20060830 just to keep it clear that
this is not necessarily a real release.

Make sure you understand the artifact version system before picking a
build number, or else you could easily end up with a situation where
the "official" plugin releases a new version but your internal plugin
is still considered "newer" ie if a plugin last released 2.0.5 and is
currently releasing 2.1-SNAPSHOT, you might want to tag yours as 2.0.6
or 2.0.5.1 -- if you tag it as 2.1, then you won't get the "real" 2.1
release when it is final. (Of course, if the plugin release 2.0.6 then
you'll get a collision there too...)

Wayne

On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
> I am using some snapshot plugins so it won't let me release.
>
>
>
> I can understand not wanting to release because of a dependency on
code
> or library snapshots, but for I don't have any issues with releasing
> something that is dependent on a snapshot of a tool, like cargo.
>
>
>
> Is there a way around this?
>
>
>
>

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

Overriding the default goal for a lifecycle phase

[LaCasse, John]

Is there any way to override the default goal for a particular phase.
For instance I would like to override the package default goal from
war:war to war:exploded since creating the war file is a lot of overhead
and I don't need it. If I specify this in the plugins section in the
package phase it just executes both war:war and war:exploded. It seems
to me that if somebody specifies a different goal for a plugin that runs
in a particular phase that it should override that plugins default.

 

Thanks,

Jpl

notice about recent assembly plugin snapshot

[John Casey]

Hi everyone,

I just wanted to send a quick note to let you know that I've made some
modifications to the way the assembly plugin functions. These changes are
likely to break your assemblies if you're using the
moduleSets/moduleSet/sources element.

The sources element used to be derived from fileSet, in that you could
provide directory, outputDirectory, includes, excludes, etc. directly on
that element. This sources element would determine how source-files from
module children and grandchildren of your project were included. In some
recent work, I've noticed that it's sometimes useful to be more flexible
with module source inclusion. So, I've made the sources element a
free-standing class, no longer derived from the fileSet.

So, to replicate this:


 
   
 src
 
   **/*.bak
   **/*~
 
   
 


you'd need to change it to the following:



 
   
 
   
 src
 
   **/*.bak
   **/*~
 
   
 
   
 


I've deployed this new snapshot for people to try out, but changes like this
and other new features of the moduleSet section are not documented yet. I'm
planning to flesh out the documentation for these new parts soon, and call a
release, as I think we're nearing a good cut-off point, before beginning a
new round of features. I just wanted to make sure I didn't leave people
saying, "WTF? This used to work!" tonight.

-john

Re: [M2] Creating archetype default directoy

[Wendy Smoak]

On 8/30/06, ccadete <[EMAIL PROTECTED]> wrote:


I want to know if this is right behavior: to put all my default package
struture after the project groupId ?


Yes.  If you want a different package structure, use
  -DpackageName=com.example.project
on the command line.

It should also be replacing ${package} inside App.java, so that
everything is in a directory structure corresponding to the package.

--
Wendy

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

[M2] Creating archetype default directoy

[ccadete]

I create an artifact with the following archetype.xml:


  simple
  
  
src/main/java/App.java
  
  



And now and I using it to create a new project,

mvn archetype:create
-DarchetypeGroupId=myarchetype  
-DarchetypeArtifactId=myarchetype
-DarchetypeVersion=1.0
-DgroupId=my.cc
-DartifactId=cc 

And see that the directory 
"src/main/java/App.java" change to "src/main/java/my/cc/App.java" in the
final project directory. The new directory struture, now have the groupId
before App.java!!

I want to know if this is right behavior: to put all my default package
struture after the project groupId ?




-- 
View this message in context: 
http://www.nabble.com/-M2--Creating-archetype-default-directoy-tf2193554.html#a6070532
Sent from the Maven - Users forum at Nabble.com.


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

[M1] QALab 0.9.1 and Maven plugin released

[Benoit Xhenseval]

Hi *,

ObjectLab is pleased to announce the release of version 0.9.1 (slowly getting 
closer to v 1.0) of QALab and its Maven 1.x plugin.

http://qalab.sourceforge.net

QA Tools like checkstyle, pmd, findbugs, cobertura (cobertura-branch and 
cobertura-line) and Simian are great build tools but they only take a snapshot 
of the state of your project. You do not get a sense of the trend of your 
project.

This project collects and consolidate data from several QA tools, like pmd, 
checkstyle, FindBugs, Cobertura and Simian and keeps track of them overtime. 
This allows developers, architects and project managers alike to be presented 
with a trend of the QA statistics of their project.

And yes... we're working on a Maven 2 plugin but if you have some spare time 
(ha!) and have developed m2 report plugin(s), we'd like to hear from you!

Many thanks!

Enjoy.

Benoit & the QALab team.

PS: the libraries should be on ibiblio.org very soon.

Re: [M2] Creating archetypes

[ccadete]

Yes, it was that, now it is working :) thanks.

ccadete

-- 
View this message in context: 
http://www.nabble.com/-M2--Creating-archetypes-tf2193156.html#a6070383
Sent from the Maven - Users forum at Nabble.com.


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

Re: [M2] Creating archetypes

[Wendy Smoak]

On 8/30/06, ccadete <[EMAIL PROTECTED]> wrote:

Now I try to create a new project using my archetype:

mvn archetype:create
-DartifactGroupId=myarchetype


Shouldn't that be -DarchetypeGroupId=myarchetype ?

Here's the README for one of mine...
http://svn.apache.org/repos/asf/struts/maven/trunk/struts-archetype-blank/README.txt

HTH,
--
Wendy

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

Re: [M2] Creating archetypes

[ccadete]

I am using:

groupId:myarchetype
artifactId:myarchetype

First, I install the project in the repository,and I see it in the directory
m2/repository/myarchetype that is the groupId directory and it is ok.

Now I try to create a new project using my archetype:

mvn archetype:create 
-DartifactGroupId=myarchetype  
-DarchetypeArtifactId=myarchetype 
-DarchetypeVersion=1.0 
-DgroupId=my.cc 
-DartifactId=cc

and it gives me:

[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error creating from archetype

Embedded error: Archetype does not exist: Unable to download the artifact
from a
ny repository

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.archetypes
-DartifactId=
myarchetype \
-Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file


  org.apache.maven.archetypes:myarchetype:jar:1.0


And we can see that the groupId is "org.apache.maven.archetypes", so it is
getting the default groupId for archetypes.







-- 
View this message in context: 
http://www.nabble.com/-M2--Creating-archetypes-tf2193156.html#a6070269
Sent from the Maven - Users forum at Nabble.com.


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

Re: [M2] Creating archetypes

[Eric Redmond]

On 8/30/06, Eric Redmond <[EMAIL PROTECTED]> wrote:


Did you actually give it a group name of "My-Archetype"? Try it again with
the dash. If it works, then yes, it might be a bug.



Woops, I meant without the dash.

Eric



On 8/30/06, ccadete <[EMAIL PROTECTED]> wrote:
>
>
>
> I installed a new my archetype, created by me, in a repository, with the
> groupId=My-Archetype, but when I choose to use it, using the
> -DarchetypeGroupID=My-Archetype in the command line, maven will try to
> download it from org.apache.maven.archetypes ( that is the default
> archetypes location ), so it will not find it.
>
> Maven try to download archetypes using the default
> "org.apache.maven.archetypes", and the option -DarchetypeGroupID does
> not
> override the default archetypes location.
>
> Is this a bug ?
>
>
>
>
> --
> View this message in context: 
http://www.nabble.com/-M2--Creating-archetypes-tf2193156.html#a6069348
>
> Sent from the Maven - Users forum at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Eric Redmond
http://codehaus.org/~eredmond 





--
Eric Redmond
http://codehaus.org/~eredmond

Re: [M2] Creating archetypes

[Wendy Smoak]

On 8/30/06, ccadete <[EMAIL PROTECTED]> wrote:


I installed a new my archetype, created by me, in a repository, with the
groupId=My-Archetype, but when I choose to use it, using the
-DarchetypeGroupID=My-Archetype in the command line, maven will try to
download it from org.apache.maven.archetypes ( that is the default
archetypes location ), so it will not find it.


(In addition to the possibly problem with the dash that Eric mentioned,)
If the archetype is not in your local repository, and not in the
central repo, you will need to use
  -DremoteRepositories=...
to tell Maven where to find it.

If you're still stuck, post the exact command you're typing, and the
error message you get.

--
Wendy

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

Re: [M2] Creating archetypes

[Eric Redmond]

Did you actually give it a group name of "My-Archetype"? Try it again with
the dash. If it works, then yes, it might be a bug.

Eric

On 8/30/06, ccadete <[EMAIL PROTECTED]> wrote:




I installed a new my archetype, created by me, in a repository, with the
groupId=My-Archetype, but when I choose to use it, using the
-DarchetypeGroupID=My-Archetype in the command line, maven will try to
download it from org.apache.maven.archetypes ( that is the default
archetypes location ), so it will not find it.

Maven try to download archetypes using the default
"org.apache.maven.archetypes", and the option -DarchetypeGroupID does not
override the default archetypes location.

Is this a bug ?




--
View this message in context:
http://www.nabble.com/-M2--Creating-archetypes-tf2193156.html#a6069348
Sent from the Maven - Users forum at Nabble.com.


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





--
Eric Redmond
http://codehaus.org/~eredmond

Re: maven-assembly-plugin: weird life cycle

[Barrie Treloar]

On 8/30/06, Alexis Midon <[EMAIL PROTECTED]> wrote:

here is what I have in my parent pom:

 
org.apache.maven.plugins
maven-assembly-plugin


src/assembly/assembly-2.1.2m.xml






Examples, sure.

But before I start, Wilfred suggested using attached but this goal
will fail in an aggregated environment. You have to use single
instead.

In my parent pom I have, ROOT/pom.xml:
my.company
product
pom
1.0-SNAPSHOT
...





org.apache.maven.plugins

maven-assembly-plugin



assembly:package
package



single






src/main/assembly/bin.xml








This binds the maven-assembly-plugin to the package phase of the
lifecycle 
(http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html)
and runs the "single" goal of the plugin.

The configuration section provides the configuration details needed
for the plugin. In this case, that the descriptor file in
src/main/assembly/bin.xml should be used.  I write my own descriptor
as I have found the built in descriptors to not be complete enough for
my environment.

By using the pluginManagement section you are telling maven then
whenever someone includes the plugin in their build section that there
are some common behaviours you want to apply and this information is
inherited if this pom is used as a parent. Not all modules will want
to create an assembly so the parent pom does not define this plugin in
the build section. So unless the module explicitly lists this plugin
in the build section having this declaration in the pluginManagement
section does nothing.

Now in one of my modules pom.xml I have, ROOT/moduleA/pom.xml:

my.company
product
1.0-SNAPSHOT

my.company
moduleA
jar
1.0-SNAPSHOT
...



org.apache.maven.plugins
maven-assembly-plugin


Notice that I have not provided any phase binding, configuration or
anything else in this declaration.  I merely state I want to use the
plugin.  This is because this pom declares a parent and therefore will
inherit this plugin configuration from the parent.

In my ROOT/moduleA/src/main/assembly/bin.xml I have:

 bin
 
   dir
   zip
 
 true
 
   
 src/main/config
 config/
 
   *
 
   
   
 target
 
 
   ${artifactId}-${version}.jar
 
   
 
 
   
 src/site/apt/index.apt
 
 README.txt
   
   
 src/main/scripts/start_debug.bat
 false
   
   
 src/main/scripts/start.bat
 false
   
   
 src/main/scripts/stop.bat
 false
   
 
 
   
 lib/
 
   ${artifactId}-${baseVersion}.${extension}
 false
   
 


HTH

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

Re: Integration Testing

[Barrie Treloar]

Joe Heck wrote

The "how to" for the separate functional test module setup was on this
earlier - the big pieces to note being that the functional test module
is set with POM packaging, and then plugins manually bound to the
various steps (in this case, the maven-surefire-plugin bound to the
integration-test phase and the cargo plugin bound to the
"pre-integration-test" phase)


Ruel Loehr wrote:

> In ant, it's pretty simple as I can just string together targets until my 
heart is content.
> With maven, I feel I am imprisoned by the lifecycle in this case.


What Joe wrote is probably the key bit here for you Ruel.

By using a pom packaging you get bugger all in the lifecycle.
Then just start binding the plugins you want to a part of the
lifecycle (you can create a new execution environment for each of your
environments)

I'm not yet up to this stage in my maven usage, so I believe it to be
technically feasible but I have not done it to know for sure.

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

Re: [POLL] Why switch to Maven?

[Jimisola Laursen]

> I agree. I don't want my site (Propellors) to be widely used... it's just
my
> own private wiki for organizing my ideas. If you notice, the page isn't
> even
> editable by the general public.

It not being editable makes it a lot easier :)

Would you consider moving your recipes to
http://docs.codehaus.org/display/MAVENUSER?

I doubt I'll find time during the week, but I could start to structure it
(the FAQ) up during the weekend.

Regards,
Jimisola

-- 
View this message in context: 
http://www.nabble.com/-POLL--Why-switch-to-Maven--tf2185174.html#a6069566
Sent from the Maven - Users forum at Nabble.com.


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

[M2] Creating archetypes

[ccadete]

I installed a new my archetype, created by me, in a repository, with the
groupId=My-Archetype, but when I choose to use it, using the
-DarchetypeGroupID=My-Archetype in the command line, maven will try to
download it from org.apache.maven.archetypes ( that is the default
archetypes location ), so it will not find it.

Maven try to download archetypes using the default
"org.apache.maven.archetypes", and the option -DarchetypeGroupID does not
override the default archetypes location.

Is this a bug ?




-- 
View this message in context: 
http://www.nabble.com/-M2--Creating-archetypes-tf2193156.html#a6069348
Sent from the Maven - Users forum at Nabble.com.


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

Re: [POLL] Why switch to Maven?

[Eric Redmond]

I agree. I don't want my site (Propellors) to be widely used... it's just my
own private wiki for organizing my ideas. If you notice, the page isn't even
editable by the general public.

On 8/30/06, Jimisola Laursen <[EMAIL PROTECTED]> wrote:



(slightly of the initial topic but...)

Hold on, hold on...

Can't we try to keep the documentation in one place? And thereby make it
easier to find.

I think that Maven Recipes is great idea, but (always a but) it's off
Maven's site.

There is a FAQ in the Codehaus Wiki that can be edited by users:

http://docs.codehaus.org/display/MAVENUSER/FAQs

However, I think that the FAQ is a bit unstructured and needs some work
(see
my previous post "Time to put some structure to Maven User FAQ on Wiki?"
on
Maven User:

http://www.nabble.com/Time-to-put-some-structure-to-Maven-User-FAQ-on-Wiki--tf2174095.html#a6012932
)

So, why not continue on documentation there the Maven Recipes there
instead.

Start something like "Maven User Documentation by Maven Users":

- FAQ (the FAQ can link to Maven Recipies when needed)
- Maven Recipies
- ...

Finally, a lot of people - including myself - seem to have been struggling
somewhat setting up Maven. Usually looking for documentation in 3-4
different places etc. I think that we all can agree on that,
but what is that we are looking for? These things should go into "Maven
User
Documentation by Maven Users" and hopefully some of things will highlight
common issues for the Maven Team and allow them to improve official
documentation, the book etc.

Regards,
Jimisola


Brett Porter wrote:
>
> That's quite cool, and along the lines of what we discussed setting up
> as the cookbook which would be blended into the site in the doc
> discussions back in June on the dev@ list (I've reposted some links
> for that recently if folks are interested in helping out with docs).
>
>
http://mail-archives.apache.org/mod_mbox/maven-dev/200608.mbox/[EMAIL PROTECTED]
>
> On 30/08/06, Rune Flobakk <[EMAIL PROTECTED]> wrote:
>> Eric Redmond wrote:
>> > I've began brainstorming on my little private wiki, if you care to
>> peek:
>> > http://www.propellors.net/wiki/index.php?title=Maven_Recipes
>>
>> Thanks for this link! Saved for future reference :)
>>
>>
>> Rune
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Apache Maven - http://maven.apache.org
> "Better Builds with Maven" book - http://library.mergere.com/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

--
View this message in context:
http://www.nabble.com/-POLL--Why-switch-to-Maven--tf2185174.html#a6068869
Sent from the Maven - Users forum at Nabble.com.


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





--
Eric Redmond
http://codehaus.org/~eredmond

Re: Spring Framework Dependencies

[Carlos Sanchez]

any questions about spring and their poms must be asked there, or you
provide the poms to be uploaded to ibiblio.

On 8/30/06, Pin Ngee Koh <[EMAIL PROTECTED]> wrote:

Do I download repository from http://www.ibiblio.org/maven2 and unzip
spring-pom-1.2.8.zip over it?
Is there a reason why we are not keeping http://www.ibiblio.org/maven2
 update to date?

On 8/30/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> see http://opensource.atlassian.com/projects/spring/browse/SPR-1484
>
> On 8/30/06, Pin Ngee Koh <[EMAIL PROTECTED]> wrote:
> > I have many artifacts which dependent on spring.
> > What's the best way to declare dependency on Spring - specifically 1.2.8?
> > I can think of the following ways:
> >
> > (1) Declare a parent pom with the right dependencies to spring-core,
> > spring-orm, ...etc. And have each project pom inherit it
> >
> > Issue: some pom does not have the right transtive dependency. E.g.
> > http://www.ibiblio.org/maven2/org/springframework/spring-core/1.2.8/
> > does not have dependency declared for commons-logging.
> >
> > (2) Declare dependency on org.springframework:spring:1.2.8. But it
> > does not include the right transitive dependencies
> >
> > Somehow, http://www.ibiblio.org/maven2 does not seems to have the
> > complete dependencies defined. Am I missing something here?
> >
> >  /
> > c=-oo
> >   \  o
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
 /
c=-oo
  \  o

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





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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

Re: [POLL] Why switch to Maven?

[Jimisola Laursen]

(slightly of the initial topic but...)

Hold on, hold on...

Can't we try to keep the documentation in one place? And thereby make it
easier to find.

I think that Maven Recipes is great idea, but (always a but) it's off
Maven's site.

There is a FAQ in the Codehaus Wiki that can be edited by users:

http://docs.codehaus.org/display/MAVENUSER/FAQs

However, I think that the FAQ is a bit unstructured and needs some work (see
my previous post "Time to put some structure to Maven User FAQ on Wiki?" on
Maven User:
http://www.nabble.com/Time-to-put-some-structure-to-Maven-User-FAQ-on-Wiki--tf2174095.html#a6012932)

So, why not continue on documentation there the Maven Recipes there instead.

Start something like "Maven User Documentation by Maven Users":

 - FAQ (the FAQ can link to Maven Recipies when needed)
 - Maven Recipies
 - ...

Finally, a lot of people - including myself - seem to have been struggling
somewhat setting up Maven. Usually looking for documentation in 3-4
different places etc. I think that we all can agree on that,
but what is that we are looking for? These things should go into "Maven User
Documentation by Maven Users" and hopefully some of things will highlight
common issues for the Maven Team and allow them to improve official
documentation, the book etc.

Regards,
Jimisola


Brett Porter wrote:
> 
> That's quite cool, and along the lines of what we discussed setting up
> as the cookbook which would be blended into the site in the doc
> discussions back in June on the dev@ list (I've reposted some links
> for that recently if folks are interested in helping out with docs).
> 
> http://mail-archives.apache.org/mod_mbox/maven-dev/200608.mbox/[EMAIL 
> PROTECTED]
> 
> On 30/08/06, Rune Flobakk <[EMAIL PROTECTED]> wrote:
>> Eric Redmond wrote:
>> > I've began brainstorming on my little private wiki, if you care to
>> peek:
>> > http://www.propellors.net/wiki/index.php?title=Maven_Recipes
>>
>> Thanks for this link! Saved for future reference :)
>>
>>
>> Rune
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> Apache Maven - http://maven.apache.org
> "Better Builds with Maven" book - http://library.mergere.com/
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-POLL--Why-switch-to-Maven--tf2185174.html#a6068869
Sent from the Maven - Users forum at Nabble.com.


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

Re: Spring Framework Dependencies

[Pin Ngee Koh]

Do I download repository from http://www.ibiblio.org/maven2 and unzip
spring-pom-1.2.8.zip over it?
Is there a reason why we are not keeping http://www.ibiblio.org/maven2
update to date?

On 8/30/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:

see http://opensource.atlassian.com/projects/spring/browse/SPR-1484

On 8/30/06, Pin Ngee Koh <[EMAIL PROTECTED]> wrote:
> I have many artifacts which dependent on spring.
> What's the best way to declare dependency on Spring - specifically 1.2.8?
> I can think of the following ways:
>
> (1) Declare a parent pom with the right dependencies to spring-core,
> spring-orm, ...etc. And have each project pom inherit it
>
> Issue: some pom does not have the right transtive dependency. E.g.
> http://www.ibiblio.org/maven2/org/springframework/spring-core/1.2.8/
> does not have dependency declared for commons-logging.
>
> (2) Declare dependency on org.springframework:spring:1.2.8. But it
> does not include the right transitive dependencies
>
> Somehow, http://www.ibiblio.org/maven2 does not seems to have the
> complete dependencies defined. Am I missing something here?
>
>  /
> c=-oo
>   \  o
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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





--
 /
c=-oo
 \  o

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

how do i turn off inclusion of all transitive dependencies? in 2.0.4

[SkipWalker]

We're having a problem with our war.  Some of the dependencies have
transitive dependencies on different versions of the same jar.

For instance, some dependency has a transitive dependency of
velocity-1.4.jar.  Another has velocity-dep-1.4.jar.  Other examples include
cglib, spring, etc.

The result is that all of these jars get included in the the war.  This can
be innocuous or problematic depending on the library.

I know that I can use the  tag in a dependency to exclude a
particular  transitive dependency.  The problem there is that I have to
track down every darn dependencies transitive dependency.  

I'd rather just explicitly state every dependency, whether they be
transitive or not, in my pom and just turn off maven's transititve
dependency resolution for my build.

Is this possible?  If so, how do I do it?

Thanks,
Skip
-- 
View this message in context: 
http://www.nabble.com/how-do-i-turn-off-inclusion-of-all-transitive-dependencies--in-2.0.4-tf2192903.html#a6068679
Sent from the Maven - Users forum at Nabble.com.


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

Re: Spring Framework Dependencies

[Carlos Sanchez]

see http://opensource.atlassian.com/projects/spring/browse/SPR-1484

On 8/30/06, Pin Ngee Koh <[EMAIL PROTECTED]> wrote:

I have many artifacts which dependent on spring.
What's the best way to declare dependency on Spring - specifically 1.2.8?
I can think of the following ways:

(1) Declare a parent pom with the right dependencies to spring-core,
spring-orm, ...etc. And have each project pom inherit it

Issue: some pom does not have the right transtive dependency. E.g.
http://www.ibiblio.org/maven2/org/springframework/spring-core/1.2.8/
does not have dependency declared for commons-logging.

(2) Declare dependency on org.springframework:spring:1.2.8. But it
does not include the right transitive dependencies

Somehow, http://www.ibiblio.org/maven2 does not seems to have the
complete dependencies defined. Am I missing something here?

 /
c=-oo
  \  o

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





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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

Re: pom files not validating

[Mykel Alvis]

My $0.02:

I used to do this, but I've since decided that it's worth the time to take
the generated POM from the maven deploy, go back to the projects (where I'm
able to), and update the POM to make it into a "real" POM instead of a
skeletal one.

I ended up with a large number of dependencies in projects that were
essentially transitive, but had to be included at the base level because
they were transitive to 3rd party dependencies, not to our actual project.
I wish people who packaged deployments to central would do this more often.

I also suggest making sure that you separate your internal repository from
your [internally-deployed EXTERNAL/3rd party] repository.  It's made a lot
of difference since I could make one of my ongoing tasks into "look for
public repositories for the 3rd party jars", such as when java-dev-net made
the javax libs available.



On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:


I deployed them with mvn deploy:deploy-file.
I had previously used mvn install:install-file and then copied them from
there to the internal repository, but there where no poms. So I then ran mvn
deploy:deploy-file.

I let maven generate the poms.

-Original Message-
From: Yann Le Du [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 1:51 PM
To: Maven Users List
Subject: Re: pom files not validating

How did you deploy your 3rd party library ? With mvn install:install-file
?
Then, did you use the generatePom option or did you write the POM yourself
?

- Yann

2006/8/30, Douglas Ferguson <[EMAIL PROTECTED]>:
>
> I have some 3rd party library dependencies that aren't in central so I
> deployed them to our internal repository.
>
>
>
> Whenever I build a project that depends on one of these libraries I get
> the following message.
>
>
>
> What can I do to get stop this?
>
>
>
> [WARNING] POM for 'uk.co.demon.windsong:crypt:pom:0.0.1:provided' is
> invalid. It will be ignored for
>
> artifact resolution. Reason: Failed to validate POM
>
>
>
> I tried deleting the pom but then it tries to go out and find it. I'd
> like to speed up the build by have the poms available.
>
>
>
> D-
>
>
>
>


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





--
I'm just an unfrozen caveman software developer.  I don't understand your
strange, "modern" ways.

Re: [maven 1.x] Need help for passing java arguments

[Arnaud HERITIER]

I found that maven.junit.jvmargs is always used (forked or not).
Thus if you don't fork your tests and you define system properties in
MAVEN_OPTS and in maven.junit.jvmargs all of them are used but in which
order ???

Arnaud

On 8/30/06, Ming Cheung <[EMAIL PROTECTED]> wrote:


Is this a bug for the maven.junit.jvmargs?


Sincerely,

Ming Cheung
WebSphere Web Services Developer

Address: IBM, Inc. 11501 Burnet Road, Austin, TX 78758
Tie Line: 678-0733
Email: [EMAIL PROTECTED]

[image: Inactive hide details for Ming Cheung/Austin/[EMAIL PROTECTED]
Cheung/Austin/[EMAIL PROTECTED]



*Ming Cheung/Austin/[EMAIL PROTECTED]

08/29/2006 04:08 PM
Please respond to
"Maven Users List" 



To

"Maven Users List" 
cc


Subject

Re: [maven 1.x] Need help for passing java arguments

Hi Arnaud,

The the java security debug is not showing afte add the following 3
properties to project.properties file.
*
maven.junit.fork=true
maven.junit.forkmode=perTest
maven.junit.jvmargs=-Djava.security.debug=all*

Sincerely,

Ming Cheung
WebSphere Web Services Developer

Address: IBM, Inc. 11501 Burnet Road, Austin, TX 78758
Tie Line: 678-0733
Email: [EMAIL PROTECTED]

"Arnaud HERITIER" <[EMAIL PROTECTED]>


  *"Arnaud HERITIER" <[EMAIL PROTECTED]>*

08/29/2006 05:30 AM

 Please respond to
"Maven Users List" 
  To

"Maven Users List"  cc
Subject

Re: [maven 1.x] Need help for passing java arguments
If you don't fork your tests you have to set these options in the
environment variable MAVEN_OPTS.
If fork is enabled you have to use the property maven.junit.jvmargs*
**http://maven.apache.org/maven-1.x/plugins/test/properties.html*

Arnaud

On 8/28/06, Ming Cheung <[EMAIL PROTECTED]> wrote:
>
>
>
> I am using maven 1.1-beta 3. When I added the
> -Dmaven.junit.jvmargs=-Djava.security.debug=all, I am unable to see the
> debug information. Could someone please tell me how to pass jvm
arguments
> [ie. -Djava.security.debug=all] to a test/project/junit test?
>
> Sincerely,
>
> Ming Cheung
> WebSphere Web Services Developer
>
> Address: IBM, Inc. 11501 Burnet Road, Austin, TX 78758
> Tie Line: 678-0733
> Email: [EMAIL PROTECTED]
>

Spring Framework Dependencies

[Pin Ngee Koh]

I have many artifacts which dependent on spring.
What's the best way to declare dependency on Spring - specifically 1.2.8?
I can think of the following ways:

(1) Declare a parent pom with the right dependencies to spring-core,
spring-orm, ...etc. And have each project pom inherit it

Issue: some pom does not have the right transtive dependency. E.g.
http://www.ibiblio.org/maven2/org/springframework/spring-core/1.2.8/
does not have dependency declared for commons-logging.

(2) Declare dependency on org.springframework:spring:1.2.8. But it
does not include the right transitive dependencies

Somehow, http://www.ibiblio.org/maven2 does not seems to have the
complete dependencies defined. Am I missing something here?

 /
c=-oo
 \  o

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

Re: [POLL] Why switch to Maven?

[Arnaud HERITIER]

You're right but I would like to add that when we deploy a snapshot we also
deploy a timestamp version of the plugin ([1] is an example for m1).
This timestamp can be used temporaly and will not be modified.
But I agree that it doesn't resolve our lake of releases

Arnaud

[1]
http://people.apache.org/repo/m1-snapshot-repository/maven/plugins/?C=M;O=D

On 8/30/06, Simon Kepp Nielsen <[EMAIL PROTECTED]> wrote:


I think this answer is one of the common problems with Maven. I don't mean
to pound on Emmanuel, who's doing a great job, but just point out a very
common problem in many open source projects.

The fact that a feature is available in a snapshot version or in the trunk
doesn't help the user that much. Unless the feature is actually released, it
doesn't do much good. My experience with Maven (and particularly the
plugins) is, that errors are often fixed quite fast after they are reported.
But from then, it can be quite a long time (often months), until the fix is
actually released. In that period, everybody affected by the bug has to use
snapshot versions, or build the plugin themselves. Snapshot versions are not
great if you are trying to run a stable build environment, and building
everything yourself from the trunk, means living on the bleeding eddge, with
lots of snapshot dependencies.

I think a good solution to the problem would be more frequent milestone
builds (both core and plugins), and a publicly available road map, giving
people a good indication of when they can expect to see what released.


Best regards

Simon Kepp Nielsen, Configurations Manager
PFA Pension, Teknisk Arkitektur
Mobile: +45 30 52 77 07
E-mail: [EMAIL PROTECTED]


PFA Pension
Sundkrogsgade 4
DK-2100 Copenhagen OE

Disclaimer
This message is for the designated recipient only and may contain
confidential or privileged information. If you have received the message in
error, please notify the sender by replying the e-mail and delete the
message without copying or disclosing.



-Oprindelig meddelelse-
Fra: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sendt: 30. august 2006 11:43
Til: Maven Users List
Emne: Re: [POLL] Why switch to Maven?



Jan Vissers a écrit :
>>> Maven's key strength is to say "don't worry about trying to build a
>>> jar / war / ear / sync with eclipse / autorun tests / publish
>>> javadocs / etc / etc, because I already know how to do that, you go
>>> and do what you do best, work on the primary code".
>
> I would like this approach very much, but...
> have you tried to publish javadocs/jxr/surefire/pmd... etc for a
> multimodule project in an aggregated fashion?

It's implemented in snapshot version of javadocs/jxr plugins

Emmanuel

>
>> On Wed, August 30, 2006 7:37 am, Jan Vissers wrote:
>>
>>> I'm reading a lot of "we need about x weeks to convert to maven",
>>> "the learning curve is steep", "it is messy but it works", "if it
>>> cannot be done we can use ant"...
>>>
>>> More and more I'm getting the feeling that ANT still isn't such a
>>> bad idea for building software. You can do a lot of the convention
>>> over configuration stuff for your own projects with ant and things
>>> like macrodef, subant and antlib. For dependency management we're
>>> currently using Ivy - which is pretty descent. What's more the
>>> reporting just works, even aggregated
>>> (pmd,jdepend,junit,checkstyle,cobertura,javadoc,changelog,javacnss).
>>>
>>> Can somebody tell me what the main reason would be for changing from
>>> ANT to Maven?
>>> I'm starting to get serious doubts.
>> I recently got involved in a project whose build system uses ant +
>> ivy, and to sum it up: what an inefficient mess.
>>
>> Within themselves, ant and ivy are worthy tools, that perform their
>> tasks well. The real problem is that once developers get hold of
>> them, things quickly go pear shaped.
>>
>> The key biggest problem with the ant + ivy combo is the fact that
>> developing the build system is a secondary concern, the primary
>> concern being developing the software itself. This causes numerous
>> problems,
>> including:
>>
>> - ant scripts are often half finished.
>>
>> In this project, nobody bothered to take advantage of incremental
builds.
>> Any attempt to build, will build clean - a huge time waster.
>>
>> - ant scripts are almost always riddled with hard coded paths, and
>> developer specific customisations.
>>
>> In this project, that means that every developer has to set up their
>> development environment the same way as the other developers, which
>> may seem perfectly acceptable to some, until you realise that
>> developers don't just work on one project.
>>
>> This makes it difficult / impossible to introduce continuous
>> integration techniques, despite this particular project desperately
needing it.
>>
>> - ant scripts are often riddled with relative paths to other
>> projects, where it is assumed a sister project is checked out.
>>
>> Again, this prevents continuous integration from being possible.
>>
>> - ivy 

RE: Integration Testing

[Heck, Joe]

We have several different mechanisms running - but most of them are
honestly manual. The automated solution that one of our teams have come
up and and stuck with is the following:

1) set up a multi-module maven2 project, with one of those modules being
a functional test suite, another the WAR that we're pushing and banging
on.
2) using cargo, we deploy the WAR produced to an instance of Tomcat
running on an available and preset QA machine.
3) We invoke the functional tests (primarily httpunit stuff) locally.

The "how to" for the separate functional test module setup was on this
earlier - the big pieces to note being that the functional test module
is set with POM packaging, and then plugins manually bound to the
various steps (in this case, the maven-surefire-plugin bound to the
integration-test phase and the cargo plugin bound to the
"pre-integration-test" phase)

We've additionally set it up so that functional tests are only included
with a specific profile (originally named "functional-tests") so that
your personal builds will invoke them only when desired.

Anything much more complex than this, and I think we'd need to reach out
of maven with a custom AntTask bound in there to do setup/teardown kinds
of work.

-joe

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ruel Loehr
Sent: Wednesday, August 30, 2006 1:33 PM
To: Maven Users List
Subject: Integration Testing

I'd like to query the community and see how you guys are handling 
integration testing in real world environments.

I've looked through the list and the Better builds book, but didn't like
what I saw..

Here is the use case:

Use Case A:

A user has a project which builds a war.   For integration testing the
war needs to be deployed in an app server.  
The process will be to startup the app server, deploy the war, run unit
tests, stop the app server.

Here is the gotcha.

App servers can have many configurations.   In this case, we would like
to test the functionality of this war on three different app server
configurations. Use case A would need to be executed 3 times
automatically, each time with a different server configuration.

Assuming I already know how to modify the appserver configs, any
suggestions on how the repeated execution of this use could be achived
in scalable fashion (e.g. if I have 25 server configurations my build
file won't be a nightmare to maintain).

In ant, it's pretty simple as I can just string together targets until
my heart is content.  With maven, I feel I am imprisoned by the
lifecycle in this case.



Ruel Loehr
JBoss, a division of Red Hat
QA
 


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.7/433 - Release Date:
8/30/2006
 

-
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: [POLL] Why switch to Maven?

[Mykel Alvis]

Preface: I make my living doing build management, and I have chosen m2
as the java build tool that I propose.

Another issue I seem to have with Maven is the difficulty in locating
(and the quality) of public repositories. I know of several (central,
codehaus, apache incubator, jboss, mvnrepository.com, java-dev-net),
and these (especially central) have varying levels of "correctness"
and "completeness".

Utilizing a proxy mechanism (in my current job I'm working with the
maven-proxy and starting to switch to proximity), I've managed to
aggregate a lot of these repositories behind the corporate firewall.

That seems to work well, but the rampant dependence on snapshots in
the plugin repositories means that I have to take the steps that were
recommended on the list (locally install a munged version of a plugin
with a fixed version number) if I want a reasonably stable build
environment.

If we had infinite time and patience, It seems like a good use of
people's time might be to scrub the central repository and create real
poms (that indicate actual transitive dependencies) rather than the
skeletal ones that are there now for a large number of projects, most
especially the ones that aren't being built by m2 in the first place.

And maybe a "listing of available repositories and their current
contents" might be useful?

--
I'm just an unfrozen caveman software developer.  I don't understand
your strange, "modern" ways.

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

Integration Testing

[Ruel Loehr]

I'd like to query the community and see how you guys are handling 
integration testing in real world environments.

I've looked through the list and the Better builds book, but didn't like what I 
saw..

Here is the use case:

Use Case A:

A user has a project which builds a war.   For integration testing the war 
needs to be deployed in an app server.  
The process will be to startup the app server, deploy the war, run unit tests, 
stop the app server.

Here is the gotcha.

App servers can have many configurations.   In this case, we would like to test 
the functionality of this war on three different app server configurations. Use 
case A would need to be executed 3 times automatically, each time with a 
different server configuration.

Assuming I already know how to modify the appserver configs, any suggestions on 
how the repeated execution of this use could be achived in scalable fashion 
(e.g. if I have 25 server configurations my build file won't be a nightmare to 
maintain).

In ant, it's pretty simple as I can just string together targets until my heart 
is content.  With maven, I feel I am imprisoned by the lifecycle in this case.



Ruel Loehr
JBoss, a division of Red Hat
QA
 


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.7/433 - Release Date: 8/30/2006
 

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

accessing continuum DB

[L. J.]

Could anyone kindly provide me a step by step instructions on how to access
the continuum DB? Also, what tool should I use?

Thanks.

LJ

Profiles - Strange Behavior

[Douglas Ferguson]

I just discovered something really odd with profiles, not sure if it is
expected.

 

I have 4 profiles.

 

Testqa.remote

Testqa.local

Localhost.remote

Localhost.local

 

I have Localhost.remote set to active via the  

 

My effective-pom contains the settings from the associated profiles when
I run with –Ptestqa.remote or –Ptestqa.local, but when I run with
-Plocalhost.local, only variables that aren’t set in localhost.remote
will appear in the effective-pom, instead the values from
localhost.remote are preserved.

 

I tried replacing the “.” with “-“ and got the same behavior.

 

If I change localhost.local to xlocalhost.local, I get my properties.

 

D-

custom information in the released POM

[Peter Neubauer]

Hi,
I would like to add some additional information as attributes/elements
to e.g. the dependency tag in the POM that is generated as the result
of a release, so the resulting tag lokos something like


   org.osgi
   osgi_R4_core
   1.0
  
 3
 true


or as attributes


   org.osgi
   osgi_R4_core
   1.0


Is it possible to have this information survive the release plugin or
what is the best way to get out such information in a standerd maven
way?

Thanks for any hints!

/peter

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

RE: pom files not validating

[Douglas Ferguson]

I deployed them with mvn deploy:deploy-file. 
I had previously used mvn install:install-file and then copied them from there 
to the internal repository, but there where no poms. So I then ran mvn 
deploy:deploy-file.

I let maven generate the poms.

-Original Message-
From: Yann Le Du [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 1:51 PM
To: Maven Users List
Subject: Re: pom files not validating

How did you deploy your 3rd party library ? With mvn install:install-file ?
Then, did you use the generatePom option or did you write the POM yourself ?

- Yann

2006/8/30, Douglas Ferguson <[EMAIL PROTECTED]>:
>
> I have some 3rd party library dependencies that aren't in central so I
> deployed them to our internal repository.
>
>
>
> Whenever I build a project that depends on one of these libraries I get
> the following message.
>
>
>
> What can I do to get stop this?
>
>
>
> [WARNING] POM for 'uk.co.demon.windsong:crypt:pom:0.0.1:provided' is
> invalid. It will be ignored for
>
> artifact resolution. Reason: Failed to validate POM
>
>
>
> I tried deleting the pom but then it tries to go out and find it. I'd
> like to speed up the build by have the poms available.
>
>
>
> D-
>
>
>
>


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

SV: [POLL] Why switch to Maven?

[Simon Kepp Nielsen]

I think this answer is one of the common problems with Maven. I don't mean to 
pound on Emmanuel, who's doing a great job, but just point out a very common 
problem in many open source projects.

The fact that a feature is available in a snapshot version or in the trunk 
doesn't help the user that much. Unless the feature is actually released, it 
doesn't do much good. My experience with Maven (and particularly the plugins) 
is, that errors are often fixed quite fast after they are reported. But from 
then, it can be quite a long time (often months), until the fix is actually 
released. In that period, everybody affected by the bug has to use snapshot 
versions, or build the plugin themselves. Snapshot versions are not great if 
you are trying to run a stable build environment, and building everything 
yourself from the trunk, means living on the bleeding eddge, with lots of 
snapshot dependencies.

I think a good solution to the problem would be more frequent milestone builds 
(both core and plugins), and a publicly available road map, giving people a 
good indication of when they can expect to see what released.


Best regards

Simon Kepp Nielsen, Configurations Manager
PFA Pension, Teknisk Arkitektur
Mobile: +45 30 52 77 07
E-mail: [EMAIL PROTECTED]


PFA Pension
Sundkrogsgade 4
DK-2100 Copenhagen OE

Disclaimer
This message is for the designated recipient only and may contain confidential 
or privileged information. If you have received the message in error, please 
notify the sender by replying the e-mail and delete the message without copying 
or disclosing.



-Oprindelig meddelelse-
Fra: Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Sendt: 30. august 2006 11:43
Til: Maven Users List
Emne: Re: [POLL] Why switch to Maven?



Jan Vissers a écrit :
>>> Maven's key strength is to say "don't worry about trying to build a 
>>> jar / war / ear / sync with eclipse / autorun tests / publish 
>>> javadocs / etc / etc, because I already know how to do that, you go 
>>> and do what you do best, work on the primary code".
> 
> I would like this approach very much, but...
> have you tried to publish javadocs/jxr/surefire/pmd... etc for a 
> multimodule project in an aggregated fashion?

It's implemented in snapshot version of javadocs/jxr plugins

Emmanuel

> 
>> On Wed, August 30, 2006 7:37 am, Jan Vissers wrote:
>>
>>> I'm reading a lot of "we need about x weeks to convert to maven", 
>>> "the learning curve is steep", "it is messy but it works", "if it 
>>> cannot be done we can use ant"...
>>>
>>> More and more I'm getting the feeling that ANT still isn't such a 
>>> bad idea for building software. You can do a lot of the convention 
>>> over configuration stuff for your own projects with ant and things 
>>> like macrodef, subant and antlib. For dependency management we're 
>>> currently using Ivy - which is pretty descent. What's more the 
>>> reporting just works, even aggregated 
>>> (pmd,jdepend,junit,checkstyle,cobertura,javadoc,changelog,javacnss).
>>>
>>> Can somebody tell me what the main reason would be for changing from 
>>> ANT to Maven?
>>> I'm starting to get serious doubts.
>> I recently got involved in a project whose build system uses ant + 
>> ivy, and to sum it up: what an inefficient mess.
>>
>> Within themselves, ant and ivy are worthy tools, that perform their 
>> tasks well. The real problem is that once developers get hold of 
>> them, things quickly go pear shaped.
>>
>> The key biggest problem with the ant + ivy combo is the fact that 
>> developing the build system is a secondary concern, the primary 
>> concern being developing the software itself. This causes numerous 
>> problems,
>> including:
>>
>> - ant scripts are often half finished.
>>
>> In this project, nobody bothered to take advantage of incremental builds.
>> Any attempt to build, will build clean - a huge time waster.
>>
>> - ant scripts are almost always riddled with hard coded paths, and 
>> developer specific customisations.
>>
>> In this project, that means that every developer has to set up their 
>> development environment the same way as the other developers, which 
>> may seem perfectly acceptable to some, until you realise that 
>> developers don't just work on one project.
>>
>> This makes it difficult / impossible to introduce continuous 
>> integration techniques, despite this particular project desperately needing 
>> it.
>>
>> - ant scripts are often riddled with relative paths to other 
>> projects, where it is assumed a sister project is checked out.
>>
>> Again, this prevents continuous integration from being possible.
>>
>> - ivy dependencies are often set up by developers who fiddle until 
>> they work.
>>
>> In this project, the eclipse jars were removed from their plugins, 
>> had their version numbers removed, and dumped into one big ivy 
>> dependency called "eclipse". There is no way of knowing what jar 
>> offers what functionality, because the jars are called sac.jar, core.jar, 
>> etc.

Re: Re: mvn2: war packaging

[Tomasz Pik]

On 8/30/06, Attila Mezei-Horvati <[EMAIL PROTECTED]> wrote:

> From: "Henry S. Isidro" <[EMAIL PROTECTED]>
> To: "Maven Users List" 
> Subject: Re: mvn2: war packaging
> Date: Wed, 30 Aug 2006 07:43:56 +0800
>
> If you're trying to include a jar in the lib folder
> of a war package, just
> declare the jar file as a dependency in the war's
> pom file. This will make
> maven automatically put it in the lib folder during
> packaging.
>
> - Henry

The problem is I am creating the jar file during the
war compilation. As I know, I can specify dependency
only for another pom jar package.

However I am running an ant task to generate code from
xsd files and compiling it. I was hoping I don't have
to move it out to a separate project; I can keep it in
this project and just copy it. Unfortunately copy
works _after_ the war is created and I don't know how
to specify the order (first copy then war). I also
tried to add it as web resource with a targetPath
option. Unfortunately that doesn't work either.


Is there a specific reason for having those files in jar?
If not, I think you may add directory, where you create your
files as 'resource' and files will be copied into 'WEB-INF/classes'
folder.

And yes - the best option will be to create separate subproject.

Regards,
Tomek

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

Re: pom files not validating

[Yann Le Du]

How did you deploy your 3rd party library ? With mvn install:install-file ?
Then, did you use the generatePom option or did you write the POM yourself ?

- Yann

2006/8/30, Douglas Ferguson <[EMAIL PROTECTED]>:


I have some 3rd party library dependencies that aren't in central so I
deployed them to our internal repository.



Whenever I build a project that depends on one of these libraries I get
the following message.



What can I do to get stop this?



[WARNING] POM for 'uk.co.demon.windsong:crypt:pom:0.0.1:provided' is
invalid. It will be ignored for

artifact resolution. Reason: Failed to validate POM



I tried deleting the pom but then it tries to go out and find it. I'd
like to speed up the build by have the poms available.



D-

pom files not validating

[Douglas Ferguson]

I have some 3rd party library dependencies that aren’t in central so I
deployed them to our internal repository.

 

Whenever I build a project that depends on one of these libraries I get
the following message.

 

What can I do to get stop this?



[WARNING] POM for 'uk.co.demon.windsong:crypt:pom:0.0.1:provided' is
invalid. It will be ignored for

 artifact resolution. Reason: Failed to validate POM

 

I tried deleting the pom but then it tries to go out and find it. I’d
like to speed up the build by have the poms available.

 

D-

Extending a plugin and parameter inheritance

[Alexis Midon]

Hi all,

I'm developping a custom plugin, its main features already are already
implemented by the antrun plugin, my only wish is to add an aggregator like
behaviour.
To do so my pojo extends the AntRunMojo, my mojo does nothing except adding
the @aggregator annotation.

Unfortunately when I package the jar, the generated plugin descriptor has no
parameters. So at runtime a NullPointerException occurs complaining that
AntRunMojo attributes are not set!

Does anybody know how to solve this problem?
Is there a neat way to extend an existing plugin?

Thanks for your help,

Alexis

Re: [maven 1.x] Need help for passing java arguments

[Ming Cheung]

Is this a bug for the maven.junit.jvmargs?

Sincerely,

Ming Cheung
WebSphere Web Services Developer

Address: IBM, Inc. 11501 Burnet Road, Austin, TX 78758
Tie Line: 678-0733
Email: [EMAIL PROTECTED]

Ming Cheung/Austin/[EMAIL PROTECTED]








Ming Cheung/Austin/[EMAIL PROTECTED] 
08/29/2006 04:08 PM

Please respond to
"Maven Users List" 








To
"Maven Users List" 


cc



Subject
Re: [maven 1.x] Need help for passing java arguments








Hi Arnaud,

The the java security debug is not showing afte add the following 3 properties to project.properties file.

maven.junit.fork=true
maven.junit.forkmode=perTest
maven.junit.jvmargs=-Djava.security.debug=all

Sincerely,

Ming Cheung
WebSphere Web Services Developer

Address: IBM, Inc. 11501 Burnet Road, Austin, TX 78758
Tie Line: 678-0733
Email: [EMAIL PROTECTED]

"Arnaud HERITIER" <[EMAIL PROTECTED]>











"Arnaud HERITIER" <[EMAIL PROTECTED]>
08/29/2006 05:30 AM 









Please respond to
"Maven Users List" 



To
"Maven Users List" 

cc

Subject
Re: [maven 1.x] Need help for passing java arguments








If you don't fork your tests you have to set these options in the
environment variable MAVEN_OPTS.
If fork is enabled you have to use the property maven.junit.jvmargs
http://maven.apache.org/maven-1.x/plugins/test/properties.html

Arnaud

On 8/28/06, Ming Cheung <[EMAIL PROTECTED]> wrote:
>
>
>
> I am using maven 1.1-beta 3. When I added the
> -Dmaven.junit.jvmargs=-Djava.security.debug=all, I am unable to see the
> debug information. Could someone please tell me how to pass jvm arguments
> [ie. -Djava.security.debug=all] to a test/project/junit test?
>
> Sincerely,
>
> Ming Cheung
> WebSphere Web Services Developer
>
> Address: IBM, Inc. 11501 Burnet Road, Austin, TX 78758
> Tie Line: 678-0733
> Email: [EMAIL PROTECTED]
>

Re: Problem with internal repository (checksum?)

[Arnaud Bailly]

"HUGOT Franck" <[EMAIL PROTECTED]> writes:

> I have an organisation repository on a tomcat server. This repository
> has been populated by all the maven plugins and my projects (this
> repository is the local repository of the maven tool installed on this
> machine so it has been automatically populated because this machine has
> internet access).

In general, using a local repository (one populated with mvn install)
a remote one is not a good idea, as the repository will lack some
important pieces of information generated at deploy time (eg. cheksum
and snapshot versions at least).

You would be better off using a mirror  such as proximity or
maven-proxy if you want/need to insulate/control what is downloaded in
dev. You should not confound proxy and mirrors: The former are just
network handlers for accessing another repo, while the latter are ful
blown replicas of another repo (eg. central).

>  
>
> Why maven download the pom from repo1 and the jar from my repository? If
> I look at my repository the pom is present.
>
>  
>
> If I replace in my settings.xml my repository id by "central" to
> override maven central repository then I get the error :
>
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does
> not exist or no valid version could be found
>

This is normal as the plugin's informations is surely missing in your
local repo. 

>
>  
>
> Because my project pom refer to this dependency maven try to download it
> from my organization repository, this works but I get this warning.
>
> Indeed, there is no checksum file for my projects installed on my
> organization repository, why? Does maven don't create this file
> automatically?
>

Yes, using deploy goal. 

> Is it because I use install-file goal? 

Right :-) 


-- 
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com


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

Nova vers�o (1.5-snapshot-cpqd-7) do plugin 'Maven Artifact Plugin' (maven:maven-artifact-plugin) dispon�vel para download

[dion]

Olá a todos,

Foi liberada uma nova versão do plugin 'Maven Artifact Plugin':

  * descrição da release: 
  * id: maven:maven-artifact-plugin
  * versão: 1.5-snapshot-cpqd-7
  * label ClearCase: MAVEN-ARTIFACT-PLUGIN-1.5-SNAPSHOT-CPQD-7

  * documentação oficial: 
  http://maven.apache.org/reference/plugins/artifact/


  * download: 
  http://baleia.cpqd.com.br:8085/maven_repository/official/maven/plugins
  
  
As principais mudanças introduzidas nessa release estão descritas abaixo

  Novas Funcionalidades:

o Adicionada a propriedade maven.repo.x.overwrite para os repositórios 
  remotos. Quando configurada para false, um deploy neste repositório será 
  abortado caso um arquivo de mesmo nome já exista. Esta propriedade só é 
  válida para os protocolos file, ftp e sftp. 

  Atualizações:

o Alteradas as classes SFtpDeployer, FtpDeployer e FileDeployer para fazer 
  verificação da flag de sobrescrita. Incluído a flag na classe 
  RepositoryInfo. Acerto da construção destes objetos em 
  RepositoryInfoBuilder.  

Para instalar o plugin, digite na linha de comando:

maven plugin:download 
  -DgroupId=maven 
  -DartifactId=maven-artifact-plugin
  -Dversion=1.5-snapshot-cpqd-7

Para a instalação manual, faça o download do seguinte jar e coloque-o no 
diretório plugins da instalação do Maven em sua máquina:

http://baleia.cpqd.com.br:8085/maven_repository/official/maven/maven-artifact-plugin-1.5-snapshot-cpqd-7.jar
 

IMPORTANTE: os passos para instalação do plugin descritos acima são 
necessários apenas nos projetos que usam o Maven customizado do CPqD.
Para os projetos que já usam o esquema de dependência de plugins via buildsys, 
não é preciso alterar nada (apenas fazer o update do buildsys na view).

   
  
  
Qualquer dúvida, envie um e-mail para [EMAIL PROTECTED]

Atenciosamente,

GAD/GCT

  

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

RE: Can't release due to SNAPSHOT dependencies

[Douglas Ferguson]

Thanks.

That makes a lot of sense...

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 10:12 AM
To: Maven Users List
Subject: Re: Can't release due to SNAPSHOT dependencies

We've talked about this before on the list, and this is the generally
suggested approach...

Download the code for the plugin(s) from SVN/CVS.
Increment the version number to a fixed/released number, build,
install locally and deploy to your corporate repo (if you have one) or
provide it to your coworkers some other way.
Update your pom to reflect the new plugin version number.

Generally I would suggest you incorporate a timestamp into the build
number ie maven-war-plugin 2.1.20060830 just to keep it clear that
this is not necessarily a real release.

Make sure you understand the artifact version system before picking a
build number, or else you could easily end up with a situation where
the "official" plugin releases a new version but your internal plugin
is still considered "newer" ie if a plugin last released 2.0.5 and is
currently releasing 2.1-SNAPSHOT, you might want to tag yours as 2.0.6
or 2.0.5.1 -- if you tag it as 2.1, then you won't get the "real" 2.1
release when it is final. (Of course, if the plugin release 2.0.6 then
you'll get a collision there too...)

Wayne

On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
> I am using some snapshot plugins so it won't let me release.
>
>
>
> I can understand not wanting to release because of a dependency on code
> or library snapshots, but for I don't have any issues with releasing
> something that is dependent on a snapshot of a tool, like cargo.
>
>
>
> Is there a way around this?
>
>
>
>

-
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: Re: mvn2: war packaging

[franz see]

Attila Mezei-Horvati wrote:
> 
>> From: "Henry S. Isidro" <[EMAIL PROTECTED]>
>> To: "Maven Users List" 
>> Subject: Re: mvn2: war packaging
>> Date: Wed, 30 Aug 2006 07:43:56 +0800
>> 
>> If you're trying to include a jar in the lib folder
>> of a war package, just 
>> declare the jar file as a dependency in the war's
>> pom file. This will make 
>> maven automatically put it in the lib folder during
>> packaging.
>> 
>> - Henry
> 
> The problem is I am creating the jar file during the
> war compilation. As I know, I can specify dependency
> only for another pom jar package.
> 
> However I am running an ant task to generate code from
> xsd files and compiling it. I was hoping I don't have
> to move it out to a separate project; I can keep it in
> this project and just copy it. Unfortunately copy
> works _after_ the war is created and I don't know how
> to specify the order (first copy then war). I also
> tried to add it as web resource with a targetPath
> option. Unfortunately that doesn't work either. 
> 
> Any ideas?
> thanks,
> Attila
> 
> __
> 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]
> 
> 
> 

Good day to you, Attila,

Specifying to include that jar file using webResouces should have worked.
However, there is a known bug that sometimes, webResources does not work.
You may want to take a look at [1] and try and apply patch2 to your
maven-war-plugin and see if your webResources would then work.

Cheers,
Franz

[1] http://jira.codehaus.org/browse/MWAR-67
-- 
View this message in context: 
http://www.nabble.com/mvn2%3A-war-packaging-tf2186390.html#a6062426
Sent from the Maven - Users forum at Nabble.com.


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

Problem with internal repository (checksum?)

[HUGOT Franck]

I have trouble with my organization repository (for maven2).

 

Here is my configuration :

 

 

I have an organisation repository on a tomcat server. This repository
has been populated by all the maven plugins and my projects (this
repository is the local repository of the maven tool installed on this
machine so it has been automatically populated because this machine has
internet access).

 

I want that all developers use this repository because they don't have
access to internet.

Developers use Eclipse on Windows XP and run maven 2 with external tools
shortcuts.

 

I try 3 scenarios :

 

-  In my settings.xml I declare my new repository (abc) and run
maven :

 

Settings.xml

 



 



   

  optional

  true

  http

  10.133.2.84

  8080

  10.133.125.36



  

 

 

   

 developpement

 



env

dev



 

 



abc

Repository interne

 
http://10.233.125.36:8080/m2repository



 

 



abc

Repository interne pour plugins

 
http://10.233.125.36:8080/m2repository



 

 

 

 

 

   developpement

 

 

 



 

The result is :

INFO] Scanning for projects...

[INFO]



[INFO] Building FWK_PRM

[INFO]task-segment: [process-resources]

[INFO]



[INFO] artifact org.apache.maven.plugins:maven-resources-plugin:
checking for updates from abc

[INFO] artifact org.apache.maven.plugins:maven-resources-plugin:
checking for updates from central

Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-p
lugin/2.2/maven-resources-plugin-2.2.pom

1/1K

1K downloaded

Downloading:
http://10.233.125.36:8080/m2repository/org/apache/maven/plugins/maven-re
sources-plugin/2.2/maven-resources-plugin-2.2.jar

4/13K

8/13K

9/13K

13/13K

13K downloaded

 

 

Why maven download the pom from repo1 and the jar from my repository? If
I look at my repository the pom is present.

 

If I replace in my settings.xml my repository id by "central" to
override maven central repository then I get the error :

 

[INFO] Scanning for projects...

[INFO]



[INFO] Building FWK_PRM

[INFO]task-segment: [process-resources]

[INFO]



[INFO] artifact org.apache.maven.plugins:maven-resources-plugin:
checking for updates from central

[INFO]


[ERROR] BUILD ERROR

[INFO]


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

[INFO]


[INFO] For more information, run Maven with the -e switch

[INFO]


[INFO] Total time: < 1 second

[INFO] Finished at: Wed Aug 30 17:55:58 CEST 2006

[INFO] Final Memory: 1M/2M

[INFO]


 

 

 

So, I try another test. I specify a proxy setting to download the
resources plugin from internet and restart the command and get this
error :

 

[INFO] Scanning for projects...

Downloading:
http://10.233.125.36:8080/m2repository/sft/framework/tru/FWK/2005.3/FWK-
2005.3.pom

1/1K

1K downloaded

[WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for
sft/framework/tru/FWK/2005.3/FWK-2005.3.pom - IGNORING

 

 

 

Because my project pom refer to this dependency maven try to download it
from my organization repository, this works but I get this warning.

Indeed, there is no checksum file for my projects installed on my
organization repository, why? Does maven don't create this file
automatically?

Is it because I use install-file goal? 

 

Thanks in advance.

 

Franck HUGOT

 

 

 

 

 

 

 

 

 

 

Re: maven-resources-plugin StringIndexOutOfBoundsException

[franz see]

chua wrote:
> 
> Hi!
> 
> I am migrating a project from m1 to m2.
> 
> I have two modeules, one to make a jar from jaxb generated and compiled
> source and another module that must create a war and which have a
> dependency with the previous jar cretaed in my jaxb module.
> 
> Well, my jaxb module works fine, the problem is when the resources are
> filtered in my second module.
> 
> I think is a problem during the execution of maven-resoures-plugin but I
> don´t know where the problem is.
> 
> I ran mvn install and the error shown is this:
> 
> ...
> ...
> ...
> [INFO]
> 
> [INFO] Building nooscom-voiceportal-web-jsf
> [INFO]task-segment: [install]
> [INFO]
> 
> [DEBUG] Skipping disabled repository Maven Snapshots
> [DEBUG] maven-war-plugin: resolved to version 2.0.2-SNAPSHOT from
> repository central
> [DEBUG] Skipping disabled repository central
> [DEBUG] maven-war-plugin: resolved to version 2.0.2-20060829.202242-1 from
> repository snapshots
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.plugins:maven-plugins::2-SNAPSHOT for project:
> null:maven-war-plugin:maven-plugin:2.0.2-20060829.202242-1 from the
> repository.
> [DEBUG] maven-plugins: resolved to version 2-20060822.131811-5 from
> repository snapshots
> [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::4-SNAPSHOT
> for project: org.apache.maven.plugins:maven-plugins:pom:2-SNAPSHOT from
> the repository.
> [DEBUG] maven-parent: resolved to version 4-20060822.161338-4 from
> repository snapshots
> [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project:
> org.apache.maven:maven-parent:pom:4-SNAPSHOT from the repository.
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-resources-plugin:2.3-SNAPSHOT:resources'
> -->
> [DEBUG]   (f) filters =
> [c:\java\workspace\nooscom-servicecopy\servicecopy/src/main/filters/desarrollo15.properties]
> [DEBUG]   (f) outputDirectory =
> c:\java\workspace\nooscom-servicecopy\servicecopy/target/classes
> [DEBUG]   (f) project = [EMAIL PROTECTED]
> [DEBUG]   (f) resources = [EMAIL PROTECTED]
> [DEBUG] -- end configuration --
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO]
> 
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] String index out of range: 0
> [INFO]
> 
> [DEBUG] Trace
> java.lang.StringIndexOutOfBoundsException: String index out of range: 0
>   at java.lang.String.charAt(String.java:558)
>   at
> org.apache.maven.plugin.resources.util.InterpolationFilterReader.read(InterpolationFilterReader.java:193)
>   at
> org.apache.maven.plugin.resources.util.InterpolationFilterReader.read(InterpolationFilterReader.java:201)
>   at
> org.apache.maven.plugin.resources.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162)
>   at java.io.Reader.read(Reader.java:122)
>   at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212)
>   at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200)
>   at
> org.apache.maven.plugin.resources.ResourcesMojo.copyFile(ResourcesMojo.java:274)
>   at
> org.apache.maven.plugin.resources.ResourcesMojo.copyResources(ResourcesMojo.java:188)
>   at
> org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:105)
>   at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
>   at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
>   at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
>   at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
>   at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
>   at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
>   at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>   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:585)
>   at org.codehaus.classworlds.Launcher.launc

eclipse:eclipse & wtp

[Douglas Ferguson]

BTW: I noticed that it actually supports 1.5.

 

But when I did so I got this error in my project. Not sure what it
means…

 

Severity and Description Path Resource  Location
Creation TimeId

Java compiler level does not match the version of the installed Java
project facet.framework Unknown
1156948862132 20524

 

  _  

From: Stefan Magnus Landrø [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 10:10 AM
To: Douglas Ferguson
Subject: Ad: wtp

 


Hi Douglas, 

just came across this in one of my poms. This is probably the best
solution. 

 
 
 
 
org.apache.maven.plugins 
 
maven-eclipse-plugin 
 
1.0 
 
 
 
 

Douglas Ferguson <[EMAIL PROTECTED]> skrev 29.08.2006
16:34:19:

> Hey, 
>   
> I was doing some reading and found some good info, but when I 
> configure a server and try to add projects to it, the available 
> projects list is empty. What am I missing? 
>   
> D-

Re: Re: [POLL] Why switch to Maven?

[Attila Mezei-Horvati]

> Date: Tue, 29 Aug 2006 17:20:07 -0500
> From: "Eric Redmond" <[EMAIL PROTECTED]>
> To: "Maven Users List" 
> Subject: Re: [POLL] Why switch to Maven?
> 
> On 8/29/06, Attila Mezei-Horvati
> <[EMAIL PROTECTED]> wrote:
> >
> > At my company we used ant to do the build files.
> > We
> > decided to switch to maven because we heard that
> > it is
> > better than ant, integrated with CI tools and it
> > can
> > build the documentation site/reports etc.
> >
> > I spent two weeks so far to move the build and I
> > still
> > am far from the goal. Sometimes I wonder if it
> > worths
> > the effort. Documentation is bad, the only way to
get
> > responses is through this group (thanks to Tamas
and
> > Chris and all others).
> >
> > There is no way from the command line for a plugin
to
> > tell what configuration options you have or what
> > goals. There is supposed to be a site generated
with
> > info but that is most of the time useless.
> > Help:describe is another tool but its not
> > telling much either.
> 
> It gives the list of mojos and all of their
> parameters, but you must use the
> "-Dfull" parameter.
 
Maybe I missed it, but I remember a couple of times I
have found properties mentioned in the site documents
which were not showing up when typed help:describe
(for ex targetPath for the war plugin).
 
I agree with an earlier post. Would be nice to have
a "help plugin parameter " command (svn was mentioned
as I recall). Would be really helpful. 

> Actually, I agree with your (and everyone elses)
> sentiment on the learning
> curve issue. I have been watching the list lately
> and have began compiling a
> list of FAQs for documenting purposes. I love the
> Mergere book, and it
> serves a purpose, however, I think that many users
> would be well servered by
> a book more along the lines of "Rails Recipies".
> Just a laundry list of:
> "How do I do X? Here's how you do X..."
> 
> I've began brainstorming on my little private
> wiki,
> if you care to peek:
>
>
http://www.propellors.net/wiki/index.php?title=Maven_Recipes
> 
Yes, this is a good idea. I was thinking to create my
own wiki for maven local. Maybe I will just try to
update this one. I know being a beginner will probably
add mistakes but I am hoping somebody will correct
that. If that is alright. 

Attila
 


__
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: archetype descriptor schema?

[franz see]

Aaron Tarter wrote:
> 
> Thanks franz for digging out the info.  That will suit my needs for now. 
> Do
> you know if there is any plan to formalize a schema?
> 
> On 8/30/06, franz see <[EMAIL PROTECTED]> wrote:
>>
>>
>> > Does anyone know where I can find the maven2 archetype descriptor
>> schema?
>> >
>> > --
>> > Regards,
>> > Aaron J Tarter
>>
>> Good day to you, Aaron,
>>
>> Maven 2 Archetype descriptor does not exactly have a DTD, but it's
>> something
>> like this:
>>
>> >   > resources?, testResources?, siteResources? )>
>>   
>>   
>>   
>>   
>>   
>>   
>>   
>>
>>   
>>   
>>   
>> ]>
>>
>> ..that is if i understand org.apache.maven.archetype.DefaultArchetype
>> correctly ^_^
>>
>> * to specify allowPartial to be true, you can put in the value "on",
>> "true",
>> or "1"...otherwise, it'll be set to false.
>>
>> * for the resource encoding, if the resource ends with .properties, the
>> encoding would be "iso-8859-1". The values available are limited to those
>> charsets supported by the Java platform, namely US-ASCII, ISO-8859-1,
>> UTF-8,
>> UTF-16BE, UTF-16LE, and UTF-16
>>
>> Cheers
>> Franz
>> --
>> View this message in context:
>> http://www.nabble.com/archetype-descriptor-schema--tf2181358.html#a6052980
>> Sent from the Maven - Users forum at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> Regards,
> Aaron J Tarter
> 
> 

Good day to you, Aaron,

Sorry, i do not. But you may want to watch and/or vote for this jira issue,
http://jira.codehaus.org/browse/ARCHETYPE-47 ^_^

Cheers,
Franz
-- 
View this message in context: 
http://www.nabble.com/archetype-descriptor-schema--tf2181358.html#a6061573
Sent from the Maven - Users forum at Nabble.com.


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

Re: mvn2: war targetPath

[Attila Mezei-Horvati]

TargetPath is not taken into account. Resources are
copied in the webroot no matter what.

Did anybody have the same issue? (see also mail
below).
thanks,
Attila

--- Attila Mezei-Horvati <[EMAIL PROTECTED]> wrote:

> I am trying to include a jar into the war file. I
> found on the site a parameter named 'targetPath'
> that
> could help me. Unfortunately it is not working for
> me.
> Can anybody point out my mistake, please.
> 
> 
> org.apache.maven.plugins
> maven-war-plugin
> 
> true
> 
> 
> 
> src
> 
> xmltypes.jar
>   
> WEB-INF/lib
> 
>  
> 
> 
> 
> No matter what I do, the jar always is copied into
> the
> webroot. I tried with xml files and only to the
> WEB-INF dir that didn't work either. Am I missing
> something?
> 
> thanks,
> Attila


__
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: NullPointerException in maven-eclipse-plugin while executing "mak e-artifacts" goal

[Sharma, Jaikumar]

Hi Stephance, 

I have created JIRA Issue for this.

http://jira.codehaus.org/browse/MECLIPSE-153

Regards

-Original Message-
From: Stéphane Bouchet [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 8:00 PM
To: Maven Users List
Subject: Re: NullPointerException in maven-eclipse-plugin while executing
"mak e-artifacts" goal

Sharma, Jaikumar a écrit :
> Thanks Stephane,
> I installed eclipse in a fresh way (only SDK -- no other plugins in IDE),
> and run "make-artifacts" and it installed all the required artifacts in
> local repository.
>
> I am still not sure why JBoss IDE artifact caused NPE.
>
> Thanks again for your help!
>
>   

You're Welcome :)

The best thing to do is to fill a new JIRA issue with your stacktrace in 
MECLIPSE ( http://jira.codehaus.org/browse/MECLIPSE ) and we will try to 
track this problem with this particular plugin.

Stéphane.

> Regards,
>
>   


-
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 Junit Test with Gigaspaces

[Wayne Fay]

We'll need to see your pom for sure, but I would assume you have not
added the proper Gigaspaces dependency/ies to your pom. Eclipse has a
tendency to find jars in lib folders and such which are not
necessarily available when executing a non-Eclipse Maven build.

Wayne

On 8/30/06, mmp <[EMAIL PROTECTED]> wrote:

Hi,

I'm currently working with Gigaspaces and created some junit-testcases to
test the functionality of my data access object.

Unfortunately when i'm running those tests with maven the GigaSpaces cannot
be found.

When I run the tests in eclipse instead, the GigaSpaces can be found.



Any ideas? Thx in advance





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

RE: Can't release due to SNAPSHOT dependencies

[Daryl.Dwyer]

The only way around it that we found was to modify the POM for the
snapshot plugin under question and release it into our team repository.
There is a good reason for not releasing code that has a snapshot
dependency on a plugin, though - the behavior of the plugin could change
resulting in the inability to reproduce the exact same build down the
road.

 

-Original Message-
From: Douglas Ferguson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 8:38 AM
To: users
Subject: Can't release due to SNAPSHOT dependencies

I am using some snapshot plugins so it won't let me release. 

 

I can understand not wanting to release because of a dependency on code
or library snapshots, but for I don't have any issues with releasing
something that is dependent on a snapshot of a tool, like cargo. 

 

Is there a way around this?



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

Site menu inheritance

[SlinnHawkins, Jon (ELS)]

Hi 
 
Could someone please give me a working example of inherited menus in their
site.xml for a parent and child project structure 
 
I would like to specify a menu in a parent project and have all child sites
inherit the said menu
 
Many Thanks

Jon

Re: Can't release due to SNAPSHOT dependencies

[Wayne Fay]

We've talked about this before on the list, and this is the generally
suggested approach...

Download the code for the plugin(s) from SVN/CVS.
Increment the version number to a fixed/released number, build,
install locally and deploy to your corporate repo (if you have one) or
provide it to your coworkers some other way.
Update your pom to reflect the new plugin version number.

Generally I would suggest you incorporate a timestamp into the build
number ie maven-war-plugin 2.1.20060830 just to keep it clear that
this is not necessarily a real release.

Make sure you understand the artifact version system before picking a
build number, or else you could easily end up with a situation where
the "official" plugin releases a new version but your internal plugin
is still considered "newer" ie if a plugin last released 2.0.5 and is
currently releasing 2.1-SNAPSHOT, you might want to tag yours as 2.0.6
or 2.0.5.1 -- if you tag it as 2.1, then you won't get the "real" 2.1
release when it is final. (Of course, if the plugin release 2.0.6 then
you'll get a collision there too...)

Wayne

On 8/30/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:

I am using some snapshot plugins so it won't let me release.



I can understand not wanting to release because of a dependency on code
or library snapshots, but for I don't have any issues with releasing
something that is dependent on a snapshot of a tool, like cargo.



Is there a way around this?






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

RE: [M2] My tests are launched 3 times !

[bdoumas]

Thanks for the answer that was what i excpected :/

So there is no way to overide the mojo declaration in  the .java

 * @execute phase="test" lifecycle="surefire"

 ... except to modify the plugin itself ...


Selon "Beyer,Nathan" <[EMAIL PROTECTED]>:

> Yes, it will run 3 times, but there's not much that can be done about
> it.
>
> Consider if you adjusted your command to "mvn clean install site". It's
> not required, but for clarity, here's what's happening. The 'clean'
> launches the clean lifecycle and cleans everything up. The 'install'
> causes the build lifecycle to run up to the 'install' phase, which
> includes the 'test' phase which runs surefire plugin. The 'site' causes
> the site lifecycle to run, which causes the surefire-report plugin to
> run and it currently doesn't use existing surefire results, so it runs
> the tests again and the cobertura plugin causes the test to run, yet
> again.
>
> There's a bug logged for this [1], but it seems like it won't be
> resolved until 2.1/2.2, if then.
>
> [1] http://jira.codehaus.org/browse/MSUREFIREREP-6
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 30, 2006 9:25 AM
> To: users@maven.apache.org
> Subject: [M2] My tests are launched 3 times !
>
> Hi all,
>
> I run a 'mvn clean site install' and my tests are launched 3 times :
>
> On for the surefire report plugin, one for the cobertura plugin and one
> for the install plugin.
>
> How can i do to have them launched only once ?
>
> Thanks !
>
> Ben
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> CONFIDENTIALITY NOTICE This message and any included attachments
> are from Cerner Corporation and are intended only for the
> addressee. The information contained in this message is
> confidential and may constitute inside or non-public information
> under international, federal, or state securities laws.
> Unauthorized forwarding, printing, copying, distribution, or use of
> such information is strictly prohibited and may be unlawful. If you
> are not the addressee, please promptly delete this message and
> notify the sender of the delivery error by e-mail or you may call
> Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
> (816)221-1024. ---
>
>
> -
> 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: archetype descriptor schema?

[Aaron Tarter]

Thanks franz for digging out the info.  That will suit my needs for now.  Do
you know if there is any plan to formalize a schema?

On 8/30/06, franz see <[EMAIL PROTECTED]> wrote:



> Does anyone know where I can find the maven2 archetype descriptor
schema?
>
> --
> Regards,
> Aaron J Tarter

Good day to you, Aaron,

Maven 2 Archetype descriptor does not exactly have a DTD, but it's
something
like this:


  
  
  
  
  
  
  

  
  
  
]>

..that is if i understand org.apache.maven.archetype.DefaultArchetype
correctly ^_^

* to specify allowPartial to be true, you can put in the value "on",
"true",
or "1"...otherwise, it'll be set to false.

* for the resource encoding, if the resource ends with .properties, the
encoding would be "iso-8859-1". The values available are limited to those
charsets supported by the Java platform, namely US-ASCII, ISO-8859-1,
UTF-8,
UTF-16BE, UTF-16LE, and UTF-16

Cheers
Franz
--
View this message in context:
http://www.nabble.com/archetype-descriptor-schema--tf2181358.html#a6052980
Sent from the Maven - Users forum at Nabble.com.


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





--
Regards,
Aaron J Tarter

RE: [M2] My tests are launched 3 times !

[Beyer,Nathan]

Yes, it will run 3 times, but there's not much that can be done about
it.

Consider if you adjusted your command to "mvn clean install site". It's
not required, but for clarity, here's what's happening. The 'clean'
launches the clean lifecycle and cleans everything up. The 'install'
causes the build lifecycle to run up to the 'install' phase, which
includes the 'test' phase which runs surefire plugin. The 'site' causes
the site lifecycle to run, which causes the surefire-report plugin to
run and it currently doesn't use existing surefire results, so it runs
the tests again and the cobertura plugin causes the test to run, yet
again.

There's a bug logged for this [1], but it seems like it won't be
resolved until 2.1/2.2, if then.

[1] http://jira.codehaus.org/browse/MSUREFIREREP-6

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 9:25 AM
To: users@maven.apache.org
Subject: [M2] My tests are launched 3 times !

Hi all,

I run a 'mvn clean site install' and my tests are launched 3 times :

On for the surefire report plugin, one for the cobertura plugin and one
for the install plugin.

How can i do to have them launched only once ?

Thanks !

Ben


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


-
CONFIDENTIALITY NOTICE This message and any included attachments
are from Cerner Corporation and are intended only for the
addressee. The information contained in this message is
confidential and may constitute inside or non-public information
under international, federal, or state securities laws.
Unauthorized forwarding, printing, copying, distribution, or use of
such information is strictly prohibited and may be unlawful. If you
are not the addressee, please promptly delete this message and
notify the sender of the delivery error by e-mail or you may call
Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
(816)221-1024. ---


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

Re: Re: mvn2: war packaging

[Attila Mezei-Horvati]

> From: "Henry S. Isidro" <[EMAIL PROTECTED]>
> To: "Maven Users List" 
> Subject: Re: mvn2: war packaging
> Date: Wed, 30 Aug 2006 07:43:56 +0800
> 
> If you're trying to include a jar in the lib folder
> of a war package, just 
> declare the jar file as a dependency in the war's
> pom file. This will make 
> maven automatically put it in the lib folder during
> packaging.
> 
> - Henry

The problem is I am creating the jar file during the
war compilation. As I know, I can specify dependency
only for another pom jar package.

However I am running an ant task to generate code from
xsd files and compiling it. I was hoping I don't have
to move it out to a separate project; I can keep it in
this project and just copy it. Unfortunately copy
works _after_ the war is created and I don't know how
to specify the order (first copy then war). I also
tried to add it as web resource with a targetPath
option. Unfortunately that doesn't work either. 

Any ideas?
thanks,
Attila

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

anyone has sample on how to expose EJBs as webservices wtih maven2 / ant/ maven1?

[Marco Mistroni]

hi all,
i am struggling in expose my ejbs as webservices .  particularlyw ith
maven2 since
wseedoclet fails to run (due to the fact that i am calling ejbdoclet task
just before)
i'd need to generate wsdl, jaxrpc-mapping and webservices.xml

managed so far only to build wsdl file (using an ant task)  and was
wondering if, in maven community, anyone
has already done it
if not, i'll go ahead struggling and once solved i'll post project and pom
on maven wiki pages

regards
marco

RE: How to deploy artifacts and its dependencies into a local proxy/repo?

[Dave Hoffer]

Yes, you are right.  I don't think the deploying has much to do with Proximity 
because Proximity doesn't yet support uploading.  We are using IIS ftp server 
to handle deploying to Proximity's repos.

My question was a general one...of how to do a private build/release of public 
artifacts that you wish were already public but aren't so you have to make it 
public for our company's developers.

-dh

-Original Message-
From: Tamás Cservenák [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 8:11 AM
To: Maven Users List
Subject: Re: How to deploy artifacts and its dependencies into a local 
proxy/repo?

Hi Dave,

it seems to me that you have no problem with _DEPLOYING_ to Proximity in
general, right? Correct me if i'm wrong.

(sigh) I have no experience with IDEA and building it's plugin.
I assume this question regards building IDEA plugin in general?


~t~


On 8/30/06, Dave Hoffer <[EMAIL PROTECTED]> wrote:
>
> Often, it seems, we have a need to use custom built public maven2
> plug-ins with our current maven2 projects.  An example of this is the
> IDEA plugin.  We need to use 2.1-SNAPSHOT because the latest released
> version 2.0 has several limitations that make it unusable.  These
> limitations have been fixed a long time ago in the IDEA plug-in trunk so
> this is what we need to use.
>
>
>
> Now what would be ideal; is for this to be released.  Second best would
> be for the IDEA developers to make publicly available snapshot releases.
> But this is a different story...assuming these can't be done I need to
> build the source and put it in our proxy (Proximity) server so it is
> available to all developers.
>
>
>
> If I get the source and run the maven install goal on each developer
> system, all is fine.   The install puts it in the user's local repo and
> they can use it just fine.  However, I want to deploy it so all don't
> need to do this.
>
>
>
> If I run the deploy goal on the single IDEA artifact it doesn't work.  I
> think this is because the IDEA plug-in has lots of dependencies that the
> deploy command line goal doesn't know about...it just deploys one
> artifact.
>
>
>
> If I try to modify the IDEA source project pom files to point to my
> distributionManagement repositories, that doesn't work either.  I get
> some build error when I run the deploy goal on the IDEA pom.  I don't
> know what the issue here is but there are lots of parent poms and it is
> likely I missed something.  In any case, this doesn't 'seem' like the
> right way to do this.
>
>
>
> What is the right way to deploy the IDEA plug-in locally into my shared
> corporate repo?
>
>
>
> -dh
>
>
>

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

Re: maven-war-plugin :

[Attila Mezei-Horvati]

Yes, I just did. It works fine for me.


  org.apache.maven.plugins
  maven-war-plugin
  
  true 
  
   

It creates a jar name with the final name I specified

 ..
   myproject
 

It adds it to the WEB-INF/lib folder. You have to do a
"mvn clean package". The simple goal war will not
recompile it and that might be the reason why you
don't see it.
This is a beginner's guess though. :)

Attila

> Date: Wed, 30 Aug 2006 13:15:51 +0200
> From: "Jeff Mutonho" <[EMAIL PROTECTED]>
> To: "Maven Users List" 
> Subject: maven-war-plugin : 
> 
> Has anyone successfully used the
> true
> parameter to bundles war class files into a jar?
> I have added it to my configuration section of
> maven-war-plugin , but it
> does not seem to have an effect.No classes jar is
> created.
> 
> -- 
> 

__
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: Re: Re: Dependency scopes

[ceki]

Thanks!


















"Martijn Dashorst" <[EMAIL PROTECTED]>
 
 
30.08.2006 16:17 
Please respond to
"Maven Users List" 



To
"Maven Users List" 
cc

Subject
Re: Re: Re: Dependency scopes



 Reviewed by Category 


Yes, but "runtime classpath" != "runtime scope"

runtime classpath == union(compile, runtime scope)

Martijn

On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> So, this means that war and ear plug-ins reference the runtime classpath
> instead of say compile or test. Correct?
>
> "Martijn Dashorst" <[EMAIL PROTECTED]> wrote on 30.08.2006
> 15:37:56:
>
> > No, but maven is also used to create war, ear and other distribution
> > packages. These packages need those actual runtime dependencies inside
> > them.
> >
> > So for testing I need junit, but not at runtime -> test scope
> > For testing I may not have a need for oracle-jdbc (using hsqldb for
> > unittests), but at runtime I will (if deploying on an oracle database)
> > -> runtime scope.
> >
> > For testing I need the interfaces for the servlet api, but those
> > interfaces are available at runtiime in the tomcat server for my web
> > application. So the servlet api JAR (javax.servlet-2.3.jar) is needed
> > for compile *and* test, but doesn't need to go into the WAR archive ->
> > provided scope.
> >
> > hth.
> >
> > Martijn
>
>
>  DISCLAIMER 
> This message is intended only for use by the person
> to whom it is addressed. It may contain information
> that is privileged and confidential. Its content does
> not constitute a formal commitment by Lombard
> Odier Darier Hentsch Group and any of its affiliates.
> If you are not the intended recipient of this message,
> kindly notify the sender immediately and destroy this
> message. Thank You.
> *
>
>


-- 
Download Wicket 1.2.2 now! New Ajax components: Tree, TreeTable and 
ModalWindow
-- http://wicketframework.org

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




 DISCLAIMER 
This message is intended only for use by the person
to whom it is addressed. It may contain information
that is privileged and confidential. Its content does
not constitute a formal commitment by Lombard
Odier Darier Hentsch Group and any of its affiliates.
If you are not the intended recipient of this message,
kindly notify the sender immediately and destroy this
message. Thank You.
*

Re: NullPointerException in maven-eclipse-plugin while executing "mak e-artifacts" goal

[Stéphane Bouchet]

Sharma, Jaikumar a écrit :

Thanks Stephane,
I installed eclipse in a fresh way (only SDK -- no other plugins in IDE),
and run "make-artifacts" and it installed all the required artifacts in
local repository.

I am still not sure why JBoss IDE artifact caused NPE.

Thanks again for your help!

  


You're Welcome :)

The best thing to do is to fill a new JIRA issue with your stacktrace in 
MECLIPSE ( http://jira.codehaus.org/browse/MECLIPSE ) and we will try to 
track this problem with this particular plugin.


Stéphane.


Regards,

  



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

[M2] My tests are launched 3 times !

[bdoumas]

Hi all,

I run a 'mvn clean site install' and my tests are launched 3 times :

On for the surefire report plugin, one for the cobertura plugin and one for the
install plugin.

How can i do to have them launched only once ?

Thanks !

Ben


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

Re: Re: Re: Dependency scopes

[Martijn Dashorst]

Yes, but "runtime classpath" != "runtime scope"

runtime classpath == union(compile, runtime scope)

Martijn

On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

So, this means that war and ear plug-ins reference the runtime classpath
instead of say compile or test. Correct?

"Martijn Dashorst" <[EMAIL PROTECTED]> wrote on 30.08.2006
15:37:56:

> No, but maven is also used to create war, ear and other distribution
> packages. These packages need those actual runtime dependencies inside
> them.
>
> So for testing I need junit, but not at runtime -> test scope
> For testing I may not have a need for oracle-jdbc (using hsqldb for
> unittests), but at runtime I will (if deploying on an oracle database)
> -> runtime scope.
>
> For testing I need the interfaces for the servlet api, but those
> interfaces are available at runtiime in the tomcat server for my web
> application. So the servlet api JAR (javax.servlet-2.3.jar) is needed
> for compile *and* test, but doesn't need to go into the WAR archive ->
> provided scope.
>
> hth.
>
> Martijn


 DISCLAIMER 
This message is intended only for use by the person
to whom it is addressed. It may contain information
that is privileged and confidential. Its content does
not constitute a formal commitment by Lombard
Odier Darier Hentsch Group and any of its affiliates.
If you are not the intended recipient of this message,
kindly notify the sender immediately and destroy this
message. Thank You.
*





--
Download Wicket 1.2.2 now! New Ajax components: Tree, TreeTable and ModalWindow
-- http://wicketframework.org

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

Re: Re: Dependency scopes

[ceki]

So, this means that war and ear plug-ins reference the runtime classpath 
instead of say compile or test. Correct?

"Martijn Dashorst" <[EMAIL PROTECTED]> wrote on 30.08.2006 
15:37:56:

> No, but maven is also used to create war, ear and other distribution
> packages. These packages need those actual runtime dependencies inside
> them.
> 
> So for testing I need junit, but not at runtime -> test scope
> For testing I may not have a need for oracle-jdbc (using hsqldb for
> unittests), but at runtime I will (if deploying on an oracle database)
> -> runtime scope.
> 
> For testing I need the interfaces for the servlet api, but those
> interfaces are available at runtiime in the tomcat server for my web
> application. So the servlet api JAR (javax.servlet-2.3.jar) is needed
> for compile *and* test, but doesn't need to go into the WAR archive ->
> provided scope.
> 
> hth.
> 
> Martijn


 DISCLAIMER 
This message is intended only for use by the person
to whom it is addressed. It may contain information
that is privileged and confidential. Its content does
not constitute a formal commitment by Lombard
Odier Darier Hentsch Group and any of its affiliates.
If you are not the intended recipient of this message,
kindly notify the sender immediately and destroy this
message. Thank You.
*

AW: [M2] Problem deploying to filesystem on remote server [SOLVED ]

[Amshoff Christoph, Köln]

Eventually, I got it...

The solution was to use backslashes (we are on Windows!) instead of slashes.
So I now have something like


  central
  FJA Internal Repository
  file:xxx\\yyy\\maven2-server\\target\\repo-local


I thought the URL should rather be in an OS independent format (using
slashes) and Maven/Java would expand to specific file path format... but
this seems not to work properly.

Boy, this was a tough one. At least, this should be documented in the guides
or BBwM book!!!

Thanx,
Christoph.


> -Ursprüngliche Nachricht-
> Von: Doug Douglass [mailto:[EMAIL PROTECTED] 
> Gesendet: Freitag, 25. August 2006 20:51
> An: Maven Users List
> Betreff: Re: [M2] Problem deploying to filesystem on remote server
> 
> 
> Hmmm, the deploy succeeds but the artifact is neither local 
> (like before)
> nor on the specified remote host?
> 
> Perhaps running maven with -X will give some more detail on 
> where the deploy
> is actually going. You might also try running the deploy 
> manually via the
> deploy:deploy-file goal with the same URL and see what happens.
> 
> Also, maybe try a different remote file:// location, just to 
> make sure it's
> not something "funny" with file://xxx/yyy.
> 
> Doug
> 
> On 8/25/06, "Amshoff Christoph, Köln" 
> <[EMAIL PROTECTED]> wrote:
> >
> > Doug,
> >
> > thanks for your reply... I was a bit surprised to get none up to now
> > ;o)  So
> > thanks a lot.
> >
> > Well, you are right, the file was put into a local 
> directory. So I changed
> > the URL to the file://host/share/some/path style:
> >
> > 
> >   central
> >   FJA Internal Repository
> >   file://xxx/yyy/maven2-server/target/repo-local
> >   false
> > 
> >
> > And now the file is not in the local directoy anymore 
> (except my local M2
> > repository, of course) -- but not on the server either!
> > Any ideas?
> >
> > Thanks,
> > Christoph.
> >
> >
> > > -Ursprüngliche Nachricht-
> > > Von: Doug Douglass [mailto:[EMAIL PROTECTED]
> > > Gesendet: Freitag, 25. August 2006 16:06
> > > An: Maven Users List
> > > Betreff: Re: [M2] Problem deploying to filesystem on remote server
> > >
> > >
> > > Christoph,
> > >
> > > Have you resolved this problem yet?
> > >
> > > I think you may find that maven deployed your artifact 
> into a local
> > > directory. Look for a directory in the root of your local
> > > filesystem with
> > > the same name as the remote host. I say this because your
> > > file url doesn't
> > > appear to be correct for a remote location. I think it should be "
> > > file://host/some/path", or if the remote location is a
> > > windows share the url
> > > should be " file://host/share/some/path".
> > >
> > > HTH,
> > > Doug
> > >
> > > On 8/23/06, "Amshoff Christoph, Köln" <
> > > [EMAIL PROTECTED]> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm new to Maven2 and trying to deploy my first JAR... 
> alas without
> > > > success
> > > > up to now.
> > > >
> > > > We are running an internal repository using Maven-Proxy
> > > (using it as a
> > > > proxy
> > > > to "central" and for hosting our own artifacts).
> > > > This is working well, and now I would like to put my 
> JARs (snapshot
> > > > version)
> > > > onto this server using the deploy goal with file system
> > > configuration.
> > > >
> > > > In my POM, I configured the settings like this:
> > > >
> > > > 
> > > >   central
> > > >   xxx
> > > >   
> file:///[a_server]/maven2-server/target/repo-local
> > > >   false
> > > > 
> > > >
> > > > The output seems to be ok, it says "551 K uploaded", but
> > > the file has NOT
> > > > been copied. Even with enabled debug information (see
> > > below) I don't see
> > > > any
> > > > problems... or is this "not adding permissions to wagon 
> connection"
> > > > telling
> > > > me anything? And yes, I have full access to the specified
> > > folder on the
> > > > remote computer.
> > > >
> > > > Is file system deploy only working locally?
> > > > What else should I use to deploy to Maven-Repo?
> > > >
> > > > Any help is appreciated...
> > > >
> > > > Thanks in advance,
> > > > Christoph.
> > > >
> > > > --- snip ---
> > > > [INFO] [deploy:deploy]
> > > > [INFO] Retrieving previous build number from central
> > > > [DEBUG] repository metadata for: 'snapshot
> > > sss:foundation:4.3.2-SNAPSHOT'
> > > > could not be found on repository: central
> > > > [DEBUG] not adding permissions to wagon connection
> > > > Uploading:
> > > >
> > > >
> > > file:///[a_server]/maven2-server/target/repo-local/xxx/yyy/4.3
> > .2-SNAPSHOT/yy
> > > y-4.3.2-SNAPSHOT.jar
> > >
> > >
> >
> > 
>  > yy-4.3.2-SNAPSHOT.jar >
> > 551K uploaded
> > [INFO] Retrieving previous metadata from central
> > [DEBUG] repository metadata for: 'artifact sss:foundation' could not be
> > found on repository: central
> > [INFO] Uploading repository metadata for: 'artifact sss:foundation'
> > [DEBUG] not adding permissions to wagon connection
> > [INFO] Retrieving previo

CSharp Plugin - Failed to resolve artifact nunit-console

[Patrick Kimber]

I am trying to build the CSharp plugin.

I have checked the source code out of Subversion and set my path to
include csc.exe.  When I run the mvn install command the build is
successful until I get to the section:

[INFO] Building Maven CSharp Exe Sample

Then I get the following error:

[ERROR] BUILD ERROR
[INFO] ---
[INFO] Failed to resolve artifact.

Missing:
--
1) nunit:nunit-console:dotnet-exe:2.2

I have tried running mvn install from the "components" folder but I
get the same error.
I have tried running mvn install from the "components\nunit" folder
and I get the error:

[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.plugins
ArtifactId: maven-csharp-lifecycle-plugin
Version: 1.0-SNAPSHOT

If the CSharp plugin project is still active I would really like to
get this working.

Thanks for your help

Patrick

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

Can't release due to SNAPSHOT dependencies

[Douglas Ferguson]

I am using some snapshot plugins so it won’t let me release. 

 

I can understand not wanting to release because of a dependency on code
or library snapshots, but for I don’t have any issues with releasing
something that is dependent on a snapshot of a tool, like cargo. 

 

Is there a way around this?

Re: Re: Dependency scopes

[Martijn Dashorst]

No, but maven is also used to create war, ear and other distribution
packages. These packages need those actual runtime dependencies inside
them.

So for testing I need junit, but not at runtime -> test scope
For testing I may not have a need for oracle-jdbc (using hsqldb for
unittests), but at runtime I will (if deploying on an oracle database)
-> runtime scope.

For testing I need the interfaces for the servlet api, but those
interfaces are available at runtiime in the tomcat server for my web
application. So the servlet api JAR (javax.servlet-2.3.jar) is needed
for compile *and* test, but doesn't need to go into the WAR archive ->
provided scope.

hth.

Martijn

On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

> On 8/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > The difference between the runtime and test scopes is also not very
> > clear to me.

"Nick Veys" <[EMAIL PROTECTED]> wrote on 17.08.2006 06:16:40:

> This was already answered, but the test dependencies aren't needed for
> "normal" runtime, so they are left out.  It allows you to pull in a
> test harness, or mock libraries during your tests but leave that out
> for "real" execution or packaging.

While I understand that certain libs may be required at compile time
but not compile time, I don't see what "normal" runtime means in terms
of Maven. Maven is a build system, it does not execute your
applications, so how can it have a runtime classpath? There is no
such thing as runtime Maven or is there?


 DISCLAIMER 
This message is intended only for use by the person
to whom it is addressed. It may contain information
that is privileged and confidential. Its content does
not constitute a formal commitment by Lombard
Odier Darier Hentsch Group and any of its affiliates.
If you are not the intended recipient of this message,
kindly notify the sender immediately and destroy this
message. Thank You.
*





--
Download Wicket 1.2.2 now! New Ajax components: Tree, TreeTable and ModalWindow
-- http://wicketframework.org

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

Re: Dependency scopes

[ceki]

> On 8/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> 
> > The difference between the runtime and test scopes is also not very
> > clear to me.

"Nick Veys" <[EMAIL PROTECTED]> wrote on 17.08.2006 06:16:40:

> This was already answered, but the test dependencies aren't needed for
> "normal" runtime, so they are left out.  It allows you to pull in a
> test harness, or mock libraries during your tests but leave that out
> for "real" execution or packaging.

While I understand that certain libs may be required at compile time
but not compile time, I don't see what "normal" runtime means in terms
of Maven. Maven is a build system, it does not execute your
applications, so how can it have a runtime classpath? There is no
such thing as runtime Maven or is there? 


 DISCLAIMER 
This message is intended only for use by the person
to whom it is addressed. It may contain information
that is privileged and confidential. Its content does
not constitute a formal commitment by Lombard
Odier Darier Hentsch Group and any of its affiliates.
If you are not the intended recipient of this message,
kindly notify the sender immediately and destroy this
message. Thank You.
*

RE: How to disable creation of cache repository under c:\Documents an d Settings\user\m2\.. ?

[Jörg Schaible]

Sharma, Jaikumar wrote on Wednesday, August 30, 2006 1:46 PM:

> Thanks Nick, But don't you think that, placing tonns of dependencies /
> plugins on every developer machine is not a sound idea ?
> Being the fact
> that theses depedencies / plugins are alreay available on intranet
> repository, why not a mechanism on demand.
> 
> Yes, If there is no way, and we want to mavenize then we have
> to go like
> this.
> 
> Although, this doest not look sound.

Unless Maven does not separate between downloaded and self-built artifacts 
installed into the local cache, it is higly dangerous to share the local repo.

- Jörg

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

Re: openoffice-maven-plugin for files in src/site/odf

[Brett Porter]

There is one included in the source distribution of Maestro (from
http://www.mergere.com/, requires registration). It requires a open
office installed and actually fires up a window for it using the OOo
java bindings.

It's about the ugliest thing I've ever seen (the OOo API is just not
very friendly - the only way to shut it down will kill any running OOo
windows you already had!), but its there (Apache Licensed) if you need
it.

Cheers,
Brett

On 05/08/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote:

Does anyone know if there is some sort of openoffice-maven-plugin
available that duplicates my odf documents as pdf, html and doc to the
generated website?

--
With kind regards,
Geoffrey De Smet


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





--
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/

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

Re: [POLL] Why switch to Maven?

[Eric Redmond]

On 8/30/06, Pierre-Yves Saumont <[EMAIL PROTECTED]> wrote:


I switched to Maven 2 because I was tired of Ant.

When one looks at a good Java project, one can find its way easyly
because there are well known architecturing and coding standards. There
are no such things with Ant. I remember trying to find my way in Ant
scripts calling other Ant scripts, and that was kind of a nightmare.
(Even with scripts I had written myself few monthes before :-)

Maven is exactly what I need. The maven way to do things might not be
the best way, but it is consistent. Consistency is much more valuable
than anything else. It is what I like the most in Java, and it is what I
like in Maven.

The big problem is documentation. The Merger book is a good
introduction, but it does not help very much to do your own work because
as soon as you need something a bit different from the example, your are
alone.

I learned the most from two chanels : The Maven 1 documentation (many
things work the same) and looking at Poms in other projects. (For
example Wicket).

What is urgently needed (IMO) is a Reference documentation with the list
of all configuration options and all possible values.

I decided to spend 6 week to learn Wicket, Maven 2 and EJB3 before I
start my next project. Until now, I am very satisfied with Wicket and
Maven 2. What I miss the most is aggregation. Some reports seems not to
aggregate at all, somes have problems (aggregating Javadoc AND Xref). I
also have problems to understand complicated transitive dependencies (I
ou're using JBoss, you better be sure that there is not a wrong version
of a jar in the classpath ;-)



Yeah, I have endless problems fighting with JBoss. So much so, that I
created a plugin at work that does the following:

product:deploy-files:
Recurse through a project (well, directory structure) and deploy all
jars,wars,ears (anything requested) to a repository w/ the same groupId and
version number (presumably the gID/version of the project, such as jboss:
4.0.4)

product:product / deploy
Generates an assembly for the remaining files (xml, directories, etc) and
builds a zip of the product with a pom, so you can deploy it to a reposiory.

product:install
Grabs the product (zip) from the repository and unpackages it to the given
directory.

What I was thinking here was a sort of "Mavenized" APT or MSI for installing
specific versions of an entire product. I'm not certain if it is an
abomination against nature, or has any merit at all (naturally, there can be
problems with exact copies of artifacts under different coordinates, eg.,
jboss:junit:4.0.4 vs junit:junit:4.0 ).


Pierre-Yves


Eric Redmond a écrit :
> Hi all Maven users!
>
> I'm beginning a study to outline the real reasons that people have for
> avoiding Maven. My questions to you all are:
> What were your anxieties about using Maven? If you use Maven: what
helped
> you make the decision? If you don't: why did you avoid it?
>
> Here are some that I have heard in the past:
>
> * Lack of good documentation.
> * Community unwilling to help me with my problems.
> * Not "industry supported" or "mainstream" enough.
> * I don't like conforming to the Maven project layout.
> * My project is too complex to switch.
> * There are not enough plugins available.
> * We already have a large investement in tool X.
> * I have to build native/non-Java code.
>
> Any more reasons? Care to expand these ideas?
> Thanks for your help!
> 
> Eric Redmond
> http://codehaus.org/~eredmond
>


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





--
Eric Redmond
http://codehaus.org/~eredmond

RE: How to disable creation of cache repository under c:\Document s an d Settings\user\m2\.. ?

[Bram de Kruijff]

> Though it seems unusual to refer it as local, it did not 
> work. I am not sure If took right steps, may be someone else 
> give some pointers on this ?

Define 'did not work'. What seems to go wrong? I think Maven does not know
(or care) wether it's a local or mounted disk. So if it doesn't work
something is wrong in your sharing configuration or the env variable
substitution.

Still when you get this to work there may be some problem when using this
with multiple developers.

1) If a developer has read-only permission and builds a project that
requires an aditional artifact it fails because it can't save the file.
Effectively it's like running mvn in offline mode.

2) Alternatively when you give all developers write permission there may be
some funny race conditions when multiple clients add the same artifact to
the shared repository.

Anyway, just add a 'clean_respository.bat' if it bothers you I'd say ;)

cheers,
Bram


> -Original Message-
> From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, August 30, 2006 1:10 PM
> To: Maven Users List
> Subject: RE: How to disable creation of cache repository 
> under c:\Document s an d Settings\user\m2\.. ?
> 
> I created a network first to try it out instead of webserver, 
> but unfortunately it did not work :
> What I did was :
> 
>   - created a network share on server.
>   - assigned write permissions on that to me 
> only, everyone read.
>   - create a environment variable in OS - WinXP
>   - and refer that environment variable in settings.xml
> 
>   ${serverShareName}
> 
> On this share, I had already placed all repository contents.
> 
> Though it seems unusual to refer it as local, it did not 
> work. I am not sure If took right steps, may be someone else 
> give some pointers on this ?
> 
> Regards.  
> 
> -Original Message-
> From: Nick Stolwijk [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 30, 2006 4:20 PM
> To: Maven Users List
> Subject: Re: How to disable creation of cache repository 
> under c:\Document s an d Settings\user\m2\.. ?
> 
> 
> I tried to say, that the programs run by Maven2 needs the jar files 
> locally. i.e. when you use Maven to compile something it calls javac 
> with a classpath set to the jar files specified in your POM. 
> Javac uses 
> the classpath to locate the jar files and as far as I know, 
> Javac can't 
> work with remote files.
> 
> What you can do is try to do create a network share and put 
> the "local" 
> repository there. I don't have any experience with this, but 
> I think it 
> may work.
> 
> HTH,
> 
> Nick Stolwijk
> 
> Sharma, Jaikumar wrote:
> > Does it mean that maven2 can not retrieve artifacts (jars etc) from 
> > remote repositories ? Or something else ? Regards.
> > 
> > -Original Message-
> > From: Nick Stolwijk [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, August 30, 2006 4:07 PM
> > To: Maven Users List
> > Subject: Re: How to disable creation of cache repository under
> > c:\Documents an d Settings\user\m2\.. ?
> > 
> > 
> > I don't think that the programs that are run by Maven2 
> (like javac and
> > java) can use remote jar files, so they have to be present on the
> local 
> > hard disk.
> > 
> > HTH,
> > 
> > Nick Stolwijk
> > 
> > Sharma, Jaikumar wrote:
> >> Is there a way to disable creation of cache repository under
> >> c:\documents and setting\user\m2\... ? I have configured local 
> >> intranet repository for plugins and dependencies.
> >>  
> >> I want this to be downloaded everytime user runs build and not to
> >> cumulate everything on every machine under C:\Documents and 
> >> Settings\user\m2\..
> >>  
> >> Thanks.
> >>  
> >> Regards.
> >>  
> >>  
> >>  
> >>  
> >> - - - - - - - DISCLAIMER- - - - - - - -
> >> Unless indicated otherwise, the information contained in 
> this message
> >> is privileged and confidential, and is intended only for 
> the use of 
> >> the
> >> addressee(s) named above and others who have been specifically
> > authorized to
> >> receive it. If you are not the intended recipient, you are hereby
> > notified
> >> that any dissemination, distribution or copying of this message 
> >> and/or attachments is strictly prohibited. The company accepts no 
> >> liability
> > for any
> >> damage caused by any virus transmitted by this email. Furthermore, 
> >> the company does not warrant a proper and complete transmission of 
> >> this information, nor does it accept liability for any 
> delays. If you
> 
> >> have received this message in error, please contact the sender and 
> >> delete
> > the
> >> message. Thank you.
> >>
> > 
> > 
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > - - - - - - - DISCLAIMER- - - - - - - -
> > Unless indicated otherwise, the information contained in 
> this message 
> > is privileged and 

Re: [POLL] Why switch to Maven?

[Wim Deblauwe]

> I would like this approach very much, but...
> have you tried to publish javadocs/jxr/surefire/pmd... etc
> for a multimodule project in an aggregated fashion?

It's implemented in snapshot version of javadocs/jxr plugins





I'm currently still on Maven 1, but I see this also as a Maven 2 problem:
plugins stay in snapshot state too long. I see many times questions asked on
the mailing list that are responded with "already fixed in the snapshot
version". Can't the Maven developers publish a new version faster? Maybe
they want to wait too long until *all known* bugs are fixed?

Wim

Maven Junit Test with Gigaspaces

[mmp]

Hi,

I'm currently working with Gigaspaces and created some junit-testcases to
test the functionality of my data access object. 

Unfortunately when i'm running those tests with maven the GigaSpaces cannot
be found.

When I run the tests in eclipse instead, the GigaSpaces can be found.

 

Any ideas? Thx in advance

Re: How to deploy artifacts and its dependencies into a local proxy/repo?

[Tamás Cservenák]

Hi Dave,

it seems to me that you have no problem with _DEPLOYING_ to Proximity in
general, right? Correct me if i'm wrong.

(sigh) I have no experience with IDEA and building it's plugin.
I assume this question regards building IDEA plugin in general?


~t~


On 8/30/06, Dave Hoffer <[EMAIL PROTECTED]> wrote:


Often, it seems, we have a need to use custom built public maven2
plug-ins with our current maven2 projects.  An example of this is the
IDEA plugin.  We need to use 2.1-SNAPSHOT because the latest released
version 2.0 has several limitations that make it unusable.  These
limitations have been fixed a long time ago in the IDEA plug-in trunk so
this is what we need to use.



Now what would be ideal; is for this to be released.  Second best would
be for the IDEA developers to make publicly available snapshot releases.
But this is a different story...assuming these can't be done I need to
build the source and put it in our proxy (Proximity) server so it is
available to all developers.



If I get the source and run the maven install goal on each developer
system, all is fine.   The install puts it in the user's local repo and
they can use it just fine.  However, I want to deploy it so all don't
need to do this.



If I run the deploy goal on the single IDEA artifact it doesn't work.  I
think this is because the IDEA plug-in has lots of dependencies that the
deploy command line goal doesn't know about...it just deploys one
artifact.



If I try to modify the IDEA source project pom files to point to my
distributionManagement repositories, that doesn't work either.  I get
some build error when I run the deploy goal on the IDEA pom.  I don't
know what the issue here is but there are lots of parent poms and it is
likely I missed something.  In any case, this doesn't 'seem' like the
right way to do this.



What is the right way to deploy the IDEA plug-in locally into my shared
corporate repo?



-dh

Re: How to disable creation of cache repository under c:\Document s an d Settings\user\m2\.. ?

[Nick Stolwijk]

I don't think that is a problem. Hard disks don't cost that much anymore 
(My local repository is now around 500 MB). The jars in the repository 
are all versioned. (as in, Maven2 automagically takes the right one, 
i.e. a specific version if you define that in your POM or a latest 
version available if you don't define it)


Maybe once in a while you can empty the repository if it really takes 
too much space and get all the needed artifacts back in as you go. Even 
if you don't have a company wide repository and thus have to get the 
artifacts from the central repositories, how long would it take with 
current day Internet speed.


And even the cost of getting it once and access them at disk speed 
versus getting them every time is in favor of getting it once.


Maybe you could replace the repository to the OS temp folder and make 
sure your temp folder is cleaned every time you boot / shutdown.


HTH,

Nick Stolwijk

Sharma, Jaikumar wrote:

Thanks Nick, But don't you think that, placing tonns of dependencies /
plugins on every developer machine is not a sound idea ? Being the fact
that theses depedencies / plugins are alreay available on intranet
repository, why not a mechanism on demand.

Yes, If there is no way, and we want to mavenize then we have to go like
this.

Although, this doest not look sound.

Regards.


-Original Message-
From: Nick Stolwijk [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 30, 2006 4:53 PM

To: Maven Users List
Subject: Re: How to disable creation of cache repository under
c:\Documents an d Settings\user\m2\.. ?


Let me ask you something else, why don't you want to cumulate everything

  on the local machines. As far as I can see, there is nothing wrong 
with that. (Maybe an exception is when the profiles you use are not 
local but remote profiles and the repository is synchronized every 
shutdown with the domain controller. Then you can move your local 
repository:


[quote from http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven2]
By default, Maven wants to place downloaded dependencies under your home

directory. On Windows, that's C:\Documents and Settings\username.DOMAIN.

(You will often see your home directory referred to as just '~' in 
documentation.) In some corporate environments, placing large numbers of


files in this location can be problematic. For example, with roaming 
profiles enabled, *everything* in that directory will be synchronized 
with the server when you log out.


To move your local repository to a different directory, place a 
'settings.xml' file in the '.m2' directory (yes, the '.' is important) 
under your home directory. (Good luck creating the '.m2' directory if it


doesn't already exist-- you'll have to do it at a command prompt as the 
Windows Explorer insists that you type a filename.)


Example:

   ~/.m2/settings.xml

   
 C:\\java\\m2-repository
   
[/quote]

HTH,

Nick Stolwijk


Sharma, Jaikumar wrote:
Is there a way to disable creation of cache repository under 
c:\documents and setting\user\m2\... ? I have configured local 
intranet repository for plugins and dependencies.
 
I want this to be downloaded everytime user runs build and not to 
cumulate everything on every machine under C:\Documents and 
Settings\user\m2\..
 
Thanks.
 
Regards.
 
 
 
 
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message 
is privileged and confidential, and is intended only for the use of 
the

addressee(s) named above and others who have been specifically

authorized to

receive it. If you are not the intended recipient, you are hereby

notified

that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability

for any

damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liability for any delays. If you have
received this message in error, please contact the sender and delete

the

message. Thank you.




-
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: Re: maven native plugin

[dan tran]

It would be great if you can enhance one of IT tests under
native-maven-plugin/src/it
to include message and resource usages as well.

-Dan

On 8/30/06, dan tran <[EMAIL PROTECTED]> wrote:




 On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> >It is not hard to allow user to override the default value, but I would
> >like to understand is first.
> I need to run the message compiler at first because it generates a
> "__.h" file, which i need in the compile step as include in many source
> files. What i did now is to copy the header file via ant task to the source
> directory.


 The message compile step should add ${project.build.directory}/native to
the include path in compile step, please file JIRA if
you dont see it show up in the compilation output


>For VS6 try to set env MSVS6_INSTALL_DIR.
> That works fine - thanks!
>
> What can i specify for the ressource compiler? I always get an error
> when runnig this step? How can i set the ressource file names?


 Please see MS rc compiler for options that you can specify.

to specifiy resource file names, use  elements like in the
compiler step.

Note both message and resource compiles are very untested areas, so you
help trouble shooting and
providing patches are very welcome.


Regards!
> Thorsten
>
>
>
> >On 8/21/06, Düvelmeyer, Thorsten < [EMAIL PROTECTED]>
> wrote:
> >>
> >> Hi,
> >>
> >> i have got two questions for native-maven-plugin:
> >>
> >> 1. Can i change the output directory for native:compile-message?
> >> I need $(base_dir) instead of ${project.build.directory}/native
> >
> >
> >Is there a reason why the current default location is not working for
> you?
> >It is not hard to
> >allow user to override the default value, but I would like to
> understand is
> >first.
> >
> >
> >
> >2. Can i set german program path of visual studio instead of english:
> >> C:\Programme\... instead of C:\Program Files\...
> >
> >
> >what version of VS do you have?
> >
> >For VS6 try to set env MSVS6_INSTALL_DIR.
> >
> >This feature is not documented yet thou.
> >
> >Where i can get the source code? The links in maven report seem to be
> old
> >> and not working.
> >
> >
> >http://svn.codehaus.org/mojo/trunk/mojo/maven-native/
> >
> >
> >
> >Thanks a lot!
> >> Thorsten
> >>
> >>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>