Re: Version conflict resolution and stable builds

[Ian Robertson]

On Sun, 2008-10-05 at 04:48 -0600, Michael McCallum wrote:
> On Sat, 04 Oct 2008 14:16:57 Keith Branton wrote:
> > 1. Can anyone please tell me of a way to achieve this with 2.0.9 today?
> With the appropriate use of ranges you can do this and it resolves as 
> described. There are about 11 gotchas to doing it though, all worked around 
> by appropriate conventions.

Can you elaborate on what these 11 gotchas are, or point to a place
which does?  

One of the biggest issues I see with ranges is that maven chooses the
most recent version in the repository which matches a given range.
Consequently, if a pom specifies a version range for a dependency like
[1.5,), the exact same code can create different builds on different
days if a new release of the dependency is made.

I'm actually curious if anyone knows the reason for this; it seams that
a far better choice would be to choose the *lowest* version which
matches all range requirements, so that builds could be temporally
stable.

  - Ian


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

Re: Need help with deploy my maven project to my remote repo.

[Tonte Pouncil]

Ok I will try this.

This worked like a champ.  Thanks for the quick reply.  I struggled with this 
for a while.  I wish I was able to find where the documentation is for this url.

Anyway thanks a million!

Tonté



- Original Message 
From: Brett Porter <[EMAIL PROTECTED]>
To: Maven Users List 
Sent: Wednesday, October 8, 2008 9:33:55 PM
Subject: Re: Need help with deploy my maven project to my remote repo.

the http deployment doesn't create all the subdirectories that would
be needed, so in this case you probably need to use dav:http://
instead.

- Brett

2008/10/9 Tonte Pouncil <[EMAIL PROTECTED]>:
> Hi,
>
> I am using maven 2.0.9 and Apache 2.2.4.  when I run the mvn deploy command I 
> get the following errors:
> [INFO] Error deploying artifact: Authorization failed: Access denied to: 
> http://XXX.XXX.XXX.XXX/[repo path]/[package name]/[project 
> name]/0.0.1-SNAPSHOT/[project name]-0.0.1-20081009.013703-1.jar
>
> In my apache error.log files i get "File does not exist" if the folder of 
> file does not already exist.
>
> But I know my apache configuration is correct bc I can create file on my 
> apache web server via DAV Explorer.
>
> Any suggestion would be helpful.
>
> Thanks!
>
> Tonté
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

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

Re: Need help with deploy my maven project to my remote repo.

[Brett Porter]

the http deployment doesn't create all the subdirectories that would
be needed, so in this case you probably need to use dav:http://
instead.

- Brett

2008/10/9 Tonte Pouncil <[EMAIL PROTECTED]>:
> Hi,
>
> I am using maven 2.0.9 and Apache 2.2.4.  when I run the mvn deploy command I 
> get the following errors:
> [INFO] Error deploying artifact: Authorization failed: Access denied to: 
> http://XXX.XXX.XXX.XXX/[repo path]/[package name]/[project 
> name]/0.0.1-SNAPSHOT/[project name]-0.0.1-20081009.013703-1.jar
>
> In my apache error.log files i get "File does not exist" if the folder of 
> file does not already exist.
>
> But I know my apache configuration is correct bc I can create file on my 
> apache web server via DAV Explorer.
>
> Any suggestion would be helpful.
>
> Thanks!
>
> Tonté
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

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

Need help with deploy my maven project to my remote repo.

[Tonte Pouncil]

Hi, 

I am using maven 2.0.9 and Apache 2.2.4.  when I run the mvn deploy command I 
get the following errors:
[INFO] Error deploying artifact: Authorization failed: Access denied to: 
http://XXX.XXX.XXX.XXX/[repo path]/[package name]/[project 
name]/0.0.1-SNAPSHOT/[project name]-0.0.1-20081009.013703-1.jar

In my apache error.log files i get "File does not exist" if the folder of file 
does not already exist.  

But I know my apache configuration is correct bc I can create file on my apache 
web server via DAV Explorer.

Any suggestion would be helpful.

Thanks!

Tonté

Re: Can't I define the parent pom's version is LATEST？

[陈思淼]

In the Maven 2.1M1 Release note ,the *Automatic* Parent Versioning has been
add to feature list, I dont think that a bad idea.

   - Addition of a prepare-package phase
   - Make-Like Reactor
Mode
(also
   coming in plugin form for Maven 2.0.x)
   - Parallel Artifact Resolution
   - PGP Artifact Verification
   - *Automatic* Parent Versioning


2008/10/9 Michael McCallum <[EMAIL PROTECTED]>

> If you really really think about all of the implications this is one of
> worst
> conventions ever proposed, its bad enough that huge numbers of projects
> have
> snapshot versions for parents in source control which means you can never
> just check out one artifact and build it... you have to get the whole mess
>
> look at what xorg and kde are doing break everything down into discreet
> components that you can build independently... it reduces the learning
> curve,
> encourages reuse and makes it easy for people to contribute
>
> On Wed, 08 Oct 2008 16:20:16 陈思淼 wrote:
> > I've vote for this issue, I think the automatic parent pom version range
> is
> > reasonable request!
> >
>
> --
> Michael McCallum
> Enterprise Engineer
> mailto:[EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: clarification on maven-site-plugin (goal - site)

[Brett Porter]

The project info reports plugin seems to be using the wrong method to
resolve the artifact. It can be safely ignored.

- Brett

2008/10/9 midnight.codder <[EMAIL PROTECTED]>:
>
> I have a project (call it A) with multiple modules (call them A1 and A2) for
> which I am trying to execute the site goal:
> org.apache.maven.plugins:maven-site-plugin:2.0-beta-7:site
>
> A1 depends on A2
> A2 depends on another in house project: nn-util
>
> nnl-util depends on nnl-common (yet another on fo our artifacts)
>
> So far this is the background.
> When I am firing up above mentioned goal I get info messages in the console
> reporting that snapshot for nnl-common was not found on all sorts of remote
> repositories, such as codehaus and java.net.
> Of course it wasn't, it is our in house artifact and we deployed it to our
> internal repository.
>
> Here is a snippet:
>
> ...
> [INFO] [project-info-reports:dependency-convergence]
> [INFO] artifact org.apache.maven.skins:maven-default-skin: checking for
> updates from archiva.group.repo
> [INFO] Using mirror: archiva.group.repo for repository: archiva.group.repo
> (mirror url: http://nnl-code.nnl.net:8080/archiva/repository/nnl-archiva)
> [INFO] [project-info-reports:dependencies]
> [INFO] artifact org.apache.maven.skins:maven-default-skin: checking for
> updates from archiva.group.repo
> [INFO] Using mirror: archiva.group.repo for repository: archiva.group.repo
> (mirror url: http://nnl-code.nnl.net:8080/archiva/repository/nnl-archiva)
> [INFO] Using mirror: archiva.group.repo for repository: archiva.group.repo
> (mirror url: http://nnl-code.nnl.net:8080/archiva/repository/nnl-archiva)
> [INFO] repository metadata for: 'snapshot nnl:nnl-common:1.0.0-SNAPSHOT'
> could not be found on repository: codehaus.snapshots, so will be created
>
> And the last line repeats itself, like I've said, for all sorts of
> repositories.
>
> Does anybody know what is the actual meaning of "so will be created"?
> Also, interesting enough, when the same goal is executed for nnl-util, that
> depends on nnl-common, no such messages are displayed. (nnl-util is a simple
> one layer project)
>
> Does anyone have an idea why is this happening? Why am I getting these
> messages?
>
>
> --
> View this message in context: 
> http://www.nabble.com/clarification-on-maven-site-plugin-%28goal---site%29-tp19887275p19887275.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

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

Re: [EclipsePlugin] downloading sources without writing .project and .classpath files

[Michael McCallum]

if you use m2eclipse then the .project files and .classpath files should be 
pretty much the same... i always put them in and thats been true of the last 
3 large commercial projects i've worked on. In all cases the environments 
were mixed windows and linux... never had a problem

On Thu, 09 Oct 2008 08:25:53 Nick Stolwijk wrote:
> And normally I exclude the .classpath and .project files from SVN.
> Each developers machine is different, so those files are also a little
> machine dependent. (plugins, filepaths, anything)
>




-- 
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]

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

Re: umlgraph & doccheck

[Brett Porter]

Try running with the javadoc debug flag and -X to see the command
actually constructed and ensure the artifact is provided correctly. I
noticed in a previous version that it hid the fact it was ignoring
some doclet artifacts.

You might also be able to upgrade to the latest release by explicitly
providing the version of the javadoc version which should report this
better now.

- Brett

2008/10/9 Matthias Dorfner <[EMAIL PROTECTED]>:
> Hi everybody,
>
>
>
> I try to integrate umlgraph and doccheck in my reporting site. I therefore 
> installed the doccheck 1.2b2 version via install-file successfully to my 
> local repository: 
> C:\Dok~\Matty\.m2\repository\com\sun\tools\doclets\doccheck\1.2b2
>
>
>
> My reporting section of the POM looks like this:
>
>
>
> …
>
> 
>
>org.apache.maven.plugins
>
>maven-javadoc-plugin
>
>
>
>  
>
>  gr.spinellis.umlgraph.doclet.UmlGraphDoc
>
>  
>
>gr.spinellis
>
>UmlGraph
>
>4.6
>
>  
>
>  
>
>  -inferrel
>
>  -inferdep
>
>  -collpackages java.util.*
>
>   
>
>
>
>
>
>  
>
>html
>
>
>
>  javadoc
>
>
>
>  
>
>  
>
>doccheck
>
>
>
>  com.sun.tools.doclet.DocCheck
>
>
>
>  
>
>  
>
>com.sun.tools.doclets
>
>doccheck
>
>1.2b2
>
>  
>
>  
>
>-d ${project.build.directory}/site/doccheck
>
>  
>
>
>
>  
>
>  doccheck
>
>
>
>  
>
>  DocCheck
>
>  DocCheck documentation.
>
>
>
>
>
>  javadoc
>
>
>
>  
>
>
>
>
>
> 
>
> …
>
>
>
> The error is following: [ERROR] BUILD ERROR
>
> [INFO]
>
> 
>
> [INFO] Error during page generation
>
>
>
> Embedded error: Error rendering Maven report: Exit code: 1 - javadoc:
>
> error - Cannot find doclet class com.sun.tools.doclet.DocCheck
>
>
>
>
>
>
>
> What am I'm doing wrong?
>
> Maybe someone can explain me the meaning of the  Tag and how I can 
> integrate these settings in my project page?
>
>
>
> Thank you in advance!
>
>
>
> Regards,
>
> Matthias
>
>
>
>
>
>
>
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

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

Re: Creating a self extracting archive with the assembly plugin

[Brett Porter]

You should create the assembly as normal, then use antrun to
concatenate the two files into a new one. The build helper can be used
to attach this new file for deployment if needed.

- Brett

2008/10/9 Zoltan Farkas <[EMAIL PROTECTED]>:
> I am migrating my maven projects from m1 to m2,
> and in m1 for deployment I was creating self extracting archives by
> concatenating a shell script with the archive.
>
> the shell script was like:
>
> #!/bin/ksh
> port=`uname`
> case $port in
>   "HP-UX") TAR="tar"
>TAIL="tail -n"
> ;;
>   "SunOS") TAR="/usr/sfw/bin/gtar"
>if test -f "$TAR"
>then
>   print "gnu tar available"
>else
>   print "gnu tar unavailable using system default"
>   TAR="tar"
>fi
>TAIL="tail"
>   ;;
>   "Linux") TAR="tar"
>TAIL="tail -n"
>   ;;
> *) TAR ="tar"
>TAIL="tail"
>   ;;
> esac
>
>  instalation script pre
> unarch.
>
>  SKIP=`awk '/^__ARCHIVE_FOLLOWS__/ { print NR + 1; exit 0; }' $0`
>  ${TAIL} +$SKIP $0 | gzip -dc | (cd $OPTIMA_HOME ; $TAR xvf -)
>
>instalation script post
> unarch.
>
>  __ARCHIVE_FOLLOWS__
>
>
> this was very useful in simplifying the installation/deployment procedure of
> my application.
>
> Is it possible to do this with the assembly plugin? If not what is the
> simplest/best way to do this?
>
> thanks
>
> --zoly
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

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

Re: maven deploy plugin help

[Brett Porter]

You can configure the deploy plugin in each of those projects to skip
deployment:
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#skip

2008/10/9 Shaun Poore <[EMAIL PROTECTED]>:
> so I'm attempting to run mvn deploy from a top level pom and I have an issue
> I was wondering if anyone had the answer to, any help is greatly
> appreciated.
>
> The top level pom builds several child pom modules.  Now I want all of the
> child poms to be deployed except for one or two when I run mvn deploy from
> the top level directory.  I'm wondering if I can specify in my pom which
> child pom's I want to be deployed or don't want deployed when I run "mvn
> deploy" from the top level directory.  I want to keep them all building the
> same but don't want to have them all deployed.
>
> Also another potential option is that all of the child projects that I don't
> want to deploy are deployed as ear or war files.  So maybe there is a way to
> specify that I only want jars to be deployed from the top level pom?
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

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

Re: Dependency range resolution resolves to SNAPSHOTS!?

[Michael McCallum]

On Thu, 09 Oct 2008 01:20:42 Mark Hobson wrote:
> 2008/10/8 Stefan Fritz <[EMAIL PROTECTED]>:
> > Hi all,
> >
> > We recently (during the last weeks) ran into a situation where version
> > ranges (e.g. [1.0,) ) where resolved to SNAPSHOT  versions as well.
> > My understanding was always that if I specify a non-snapshot version in a
where does it say that in the docs? Maybe I missed it.

> > range that only released version will be resolved.
> >
> > Is my understanding incorrect or is there a bug in dependency resolution?
> >
> > I'm using 2.0.9
>
> This is indeed a bug, see:
>
> http://jira.codehaus.org/browse/MNG-3092

I still disgree, its absolutely necessary for agile development. 

If you consider that every version just a number and you use interval notation 
then of course snapshots are going to fall into the range somewhere.

The argument is 'are SNAPSHOTS really useful at all?' and the answer is 'they 
are but only when governed by appropriate development practice'. 

If you go and SNAPSHOT things all over the place and deploy them to remote 
repositories I would argue that you should just not use maven go back to make 
or ant because you have not made the transition to understand how powerful 
maven dependency resolution can be for development and _deploying_ with 
determinability. I stay away from reproducibility because thats the other end 
of the scale from agile and convention.

My goal is to develop fast and know the result, potentially break but be able 
to recover from a break _very_ quickly. Carry out multiple lines of 
development without the need for costly source control merges. Branch and 
patch easily and always stay in a state of release readiness. You can do all 
of this without making the ramp up significant. 

To digress slightly when unit testing in order to be sure you are actually 
proving anything you can't have SNAPSHOTS with one exception if I as a 
developer injected that SNAPSHOT into the resolution tree for a reason i.e. 
to see if it breaks the test and why or not. If I have other peoples 
SNAPSHOTS I have no easy process for figuring out how and why things are 
breaking and how to achieve the fix, no way to roll forward and back to 
isolate faults.

my 2[00] cents :-/

-- 
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]

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

Re: evaluation report-history tools (e.g. xradar, sonar)

[Kalle Korhonen]

Hudson supports trendlines for build & test failures, code coverage and
static analysis. We use Maven dashboard plugin as well, but Hudson is more
up-to-date and easier to use. For source control stats we use statsvn. I'd
be interested in your experiences if you decide to give Sonar a try (I
looked at 1.0.x versions, decided at the time it wasn't quite stable enough
for our use).

Kalle


On Wed, Oct 8, 2008 at 12:50 PM, Rémy Sanlaville
<[EMAIL PROTECTED]>wrote:

> Hi,
>
> We tried Qalab one year ago but we had some strange/incorrect results and
> it
> does not evolve anymore.
> We are thinking about using Sonar now.
>
> Rémy
>

Re: Can't I define the parent pom's version is LATEST？

[Michael McCallum]

If you really really think about all of the implications this is one of worst 
conventions ever proposed, its bad enough that huge numbers of projects have 
snapshot versions for parents in source control which means you can never 
just check out one artifact and build it... you have to get the whole mess

look at what xorg and kde are doing break everything down into discreet 
components that you can build independently... it reduces the learning curve, 
encourages reuse and makes it easy for people to contribute

On Wed, 08 Oct 2008 16:20:16 陈思淼 wrote:
> I've vote for this issue, I think the automatic parent pom version range is
> reasonable request!
>

-- 
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]

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

clarification on maven-site-plugin (goal - site)

[midnight.codder]

I have a project (call it A) with multiple modules (call them A1 and A2) for
which I am trying to execute the site goal:
org.apache.maven.plugins:maven-site-plugin:2.0-beta-7:site

A1 depends on A2
A2 depends on another in house project: nn-util

nnl-util depends on nnl-common (yet another on fo our artifacts)

So far this is the background.
When I am firing up above mentioned goal I get info messages in the console
reporting that snapshot for nnl-common was not found on all sorts of remote
repositories, such as codehaus and java.net. 
Of course it wasn't, it is our in house artifact and we deployed it to our
internal repository.

Here is a snippet:

...
[INFO] [project-info-reports:dependency-convergence]
[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for
updates from archiva.group.repo
[INFO] Using mirror: archiva.group.repo for repository: archiva.group.repo
(mirror url: http://nnl-code.nnl.net:8080/archiva/repository/nnl-archiva)
[INFO] [project-info-reports:dependencies]
[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for
updates from archiva.group.repo
[INFO] Using mirror: archiva.group.repo for repository: archiva.group.repo
(mirror url: http://nnl-code.nnl.net:8080/archiva/repository/nnl-archiva)
[INFO] Using mirror: archiva.group.repo for repository: archiva.group.repo
(mirror url: http://nnl-code.nnl.net:8080/archiva/repository/nnl-archiva)
[INFO] repository metadata for: 'snapshot nnl:nnl-common:1.0.0-SNAPSHOT'
could not be found on repository: codehaus.snapshots, so will be created

And the last line repeats itself, like I've said, for all sorts of
repositories.

Does anybody know what is the actual meaning of "so will be created"?
Also, interesting enough, when the same goal is executed for nnl-util, that
depends on nnl-common, no such messages are displayed. (nnl-util is a simple
one layer project)

Does anyone have an idea why is this happening? Why am I getting these
messages?


-- 
View this message in context: 
http://www.nabble.com/clarification-on-maven-site-plugin-%28goal---site%29-tp19887275p19887275.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Can maven generate this kind report?

[Rémy Sanlaville]

Hi,

You can have a look also to the scmchangelog-maven-plugin (
http://mojo.codehaus.org/scmchangelog-maven-plugin/).

We are working for it's first release in few days.

Rémy

Re: evaluation report-history tools (e.g. xradar, sonar)

[Rémy Sanlaville]

Hi,

We tried Qalab one year ago but we had some strange/incorrect results and it
does not evolve anymore.
We are thinking about using Sonar now.

Rémy

Re: evaluation report-history tools (e.g. xradar, sonar)

[Geoffrey Wiseman]

On Tue, Oct 7, 2008 at 9:38 PM, Michael McCallum <[EMAIL PROTECTED]> wrote:

>  no experience but from having looked at
> the
> projects they all follow a similar flawed approach... store the results of
> runs in a database somewhere
>
> the tools are good according to people i know who have used them...
>

I've used Sonar.  It's not bad at what it does.  I do wish it was just
integrated into Maven Site, tho.

  - Geoffrey
-- 
Geoffrey Wiseman

Re: [EclipsePlugin] downloading sources without writing .project and .classpath files

[Nick Stolwijk]

And normally I exclude the .classpath and .project files from SVN.
Each developers machine is different, so those files are also a little
machine dependent. (plugins, filepaths, anything)

Hth,

Nick Stolwijk
~Java Developer~

Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl



On Wed, Oct 8, 2008 at 9:15 PM, Thor <[EMAIL PROTECTED]> wrote:
> Use the dependency plugin: mvn dependency:sources
> http://maven.apache.org/plugins/maven-dependency-plugin/
>
>
>
>
> On Wed, Oct 8, 2008 at 5:00 AM, Andreas Riedel <[EMAIL PROTECTED]>wrote:
>
>> Hello List.
>>
>> I've a question by using the Eclipse Plugin.
>> We will dispose the Q4E Eclipse Plugin.
>>
>> So call the Plugin with:
>> mvn eclipse:eclipse -DdownloadSources=true
>>
>> works fine.
>>
>> But the writen .project and .classpath files are shared by SVN. So the
>> other developer aren't beholden to run write the .project and .classpath
>> files new.
>> So, is it possible to download the sources by the plugin but don't write
>> the .project and .classpath files again and again.
>>
>> TIA
>> Andreas
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> (o_  \*/   \  /
> / / )_  |   |  O  |
> v  v  In a free world...
>

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

Re: [EclipsePlugin] downloading sources without writing .project and .classpath files

[Thor]

Use the dependency plugin: mvn dependency:sources
http://maven.apache.org/plugins/maven-dependency-plugin/




On Wed, Oct 8, 2008 at 5:00 AM, Andreas Riedel <[EMAIL PROTECTED]>wrote:

> Hello List.
>
> I've a question by using the Eclipse Plugin.
> We will dispose the Q4E Eclipse Plugin.
>
> So call the Plugin with:
> mvn eclipse:eclipse -DdownloadSources=true
>
> works fine.
>
> But the writen .project and .classpath files are shared by SVN. So the
> other developer aren't beholden to run write the .project and .classpath
> files new.
> So, is it possible to download the sources by the plugin but don't write
> the .project and .classpath files again and again.
>
> TIA
> Andreas
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
(o_  \*/   \  /
/ / )_  |   |  O  |
 v  v  In a free world...

Re: [OT somewhat] commit modules separately or all under one project?

[Geoffrey Wiseman]

On Wed, Oct 8, 2008 at 11:33 AM, Rick <[EMAIL PROTECTED]> wrote:

> In a typical JEE project I have a parent module that my children all
> inherit from. My modules look like:
>
> parent
>   ear
>   ejb
>   web
>   jar
>
> My debate is how to best put this into version control? Do most of you
> commit the parent directory that holds all the submodules as 'one
> project' or do some of you like to commit each module separately? I'm
> leaning towards just checking in the whole parent directory as one
> project, since the modules are all so closely related. Although the
> jar file (Which is mostly util stuff can really be stand alone I
> suppose and in theory the ejb module could be used by another web
> project, but that's extremely unlikely.  )
>

Depends a lot on the specifics.  For the most part, I'll commit this kind of
work as a single project.  Where I feel like there are truly re-usable
elements (things that I will reuse, not "might reuse"), I'll tend to
separate those and only those into their own top-level projects.

In essence, if a group of modules are likely to change together and be
released and deployed together, I'll treat them as a single project with
modules.  When one or more of those starts to develop its own lifecycle,
I'll start splitting them off into their own projects.

Make sense?

  - Geoffery

-- 
Geoffrey Wiseman

Re: what's the maven main version meaning?

[Wendy Smoak]

On Wed, Oct 8, 2008 at 9:36 AM, 陈思淼 <[EMAIL PROTECTED]> wrote:
> now the Apache Maven 2.1.0-M1
> Released
> .
> what's the M1 meaning? and when will the final version to be released?

IM1 means it is the first 'Milestone' release of Maven 2.1.0.

The release plan is on the wiki [1].  Come join us on the dev list if
you want to discuss features and possible release dates. :)

[1] http://docs.codehaus.org/display/MAVEN/Maven+2.1.0+Release+Plan

-- 
Wendy

umlgraph & doccheck

[Matthias Dorfner]

Hi everybody,

 

I try to integrate umlgraph and doccheck in my reporting site. I therefore 
installed the doccheck 1.2b2 version via install-file successfully to my local 
repository: C:\Dok~\Matty\.m2\repository\com\sun\tools\doclets\doccheck\1.2b2

 

My reporting section of the POM looks like this:

 

…



org.apache.maven.plugins

maven-javadoc-plugin



  

  gr.spinellis.umlgraph.doclet.UmlGraphDoc

  

gr.spinellis

UmlGraph

4.6

  

  

  -inferrel

  -inferdep

  -collpackages java.util.*

   





  

html



  javadoc



  

  

doccheck



  com.sun.tools.doclet.DocCheck

 

  

  

com.sun.tools.doclets

doccheck

1.2b2

  

  

-d ${project.build.directory}/site/doccheck

  

 

  

  doccheck

 

  

  DocCheck

  DocCheck documentation.





  javadoc



  



 

 

…

 

The error is following: [ERROR] BUILD ERROR

[INFO]



[INFO] Error during page generation

 

Embedded error: Error rendering Maven report: Exit code: 1 - javadoc:

error - Cannot find doclet class com.sun.tools.doclet.DocCheck

 

 

 

What am I’m doing wrong?

Maybe someone can explain me the meaning of the  Tag and how I can 
integrate these settings in my project page?

 

Thank you in advance!

 

Regards,

Matthias

 

 

 

what's the maven main version meaning?

[陈思淼]

now the Apache Maven 2.1.0-M1
Released
.
what's the M1 meaning? and when will the final version to be released?

Creating a self extracting archive with the assembly plugin

[Zoltan Farkas]

I am migrating my maven projects from m1 to m2,
and in m1 for deployment I was creating self extracting archives by 
concatenating a shell script with the archive.


the shell script was like:

#!/bin/ksh
port=`uname`
case $port in
   "HP-UX") TAR="tar"
TAIL="tail -n"
 ;;
   "SunOS") TAR="/usr/sfw/bin/gtar"
if test -f "$TAR"
then
   print "gnu tar available"
else
   print "gnu tar unavailable using system default"
   TAR="tar"
fi
TAIL="tail"
   ;;
   "Linux") TAR="tar"
TAIL="tail -n"
   ;;
 *) TAR ="tar"
TAIL="tail"
   ;;
esac

  instalation script pre 
unarch.


  SKIP=`awk '/^__ARCHIVE_FOLLOWS__/ { print NR + 1; exit 0; }' $0`
  ${TAIL} +$SKIP $0 | gzip -dc | (cd $OPTIMA_HOME ; $TAR xvf -)

instalation script post 
unarch.


 __ARCHIVE_FOLLOWS__


this was very useful in simplifying the installation/deployment 
procedure of my application.


Is it possible to do this with the assembly plugin? If not what is the 
simplest/best way to do this?


thanks

--zoly


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

maven deploy plugin help

[Shaun Poore]

so I'm attempting to run mvn deploy from a top level pom and I have an issue
I was wondering if anyone had the answer to, any help is greatly
appreciated.

The top level pom builds several child pom modules.  Now I want all of the
child poms to be deployed except for one or two when I run mvn deploy from
the top level directory.  I'm wondering if I can specify in my pom which
child pom's I want to be deployed or don't want deployed when I run "mvn
deploy" from the top level directory.  I want to keep them all building the
same but don't want to have them all deployed.

Also another potential option is that all of the child projects that I don't
want to deploy are deployed as ear or war files.  So maybe there is a way to
specify that I only want jars to be deployed from the top level pom?

Re: How to use Maven with multiple repositories?

[midnight.codder]

Thanks Brett,

I started from the second option but it did not work.

However using the repositories group (called virtual repository in Archiva)
worked like a charm.

We are now one step closer to a happier and smooth sailing build!

Thanks.


Brett Porter wrote:
> 
> Because of the mirror setting, everything is going to be redirected to
> your internal repository.
> 
> You have two options:
> 1) point this to a group on the server, and have that group dictate
> which repositories are used
> 2) add additional mirrors for different repositories (they are keyed by
> the ID).
> 
> Hope that helps.
> 
> Cheers,
> Brett
> 
> 2008/10/7 midnight.codder <[EMAIL PROTECTED]>:
>>
>> I have read the setting reference and the POM reference probably a
>> gazillion
>> times and searched this forum for similar posts, and even found them (!)
>> but
>> the solution proposed therein did not work for me at all.
>>
>> We are using Archiva as our internal repository. On Archiva we have 3
>> repositories, 2 for third party artifacts (one for snapshot and one for
>> releases) and one for our artifacts (we have just began and just trying
>> to
>> get up and running, so releases and snapshot at still together).
>> I can get the deploy goal to deploy my artifact to my group's repository.
>> But my colleague cannot compile his module which depends on the artifact
>> I
>> just deployed.
>>
>> I declared those repositories in repositories tags in a profile tag and
>> activated it in the setting.xml (attached) - but it makes no difference.
>> Maven can't locate the artifact.
>>
>> A very confusing paragraph in the setting reference got me thinking that
>> I
>> just don't understand Maven enough or have problems with reading
>> comprehension (or both):
>>
>> The final piece of the settings.xml puzzle is the activeProfiles element.
>> This contains a set of activeProfile elements, which each have a value of
>> a
>> profile id. Any profile id defined as an activeProfile will be active,
>> reguardless of any environment settings. If no matching profile is found
>> nothing will happen. For example, if env-test is an activeProfile, a
>> profile
>> in a pom.xml (or profile.xml with a corrosponding id will be active. If
>> no
>> such profile is found then execution will continue as normal.
>>
>> So I thought maybe I am missing a profile tag in the pom.xml of my
>> project.
>> I tried adding that but it did not do squat.
>>
>> setting.xml is attached and the project's pom.xml too.
>> A link to a very similar post (to the best of my understanding I tried
>> the
>> solution, but no success):
>> http://www.nabble.com/-m2--multiple-repository-confusion-td978358.html#a978358
>>
>> Thanks.
>> http://www.nabble.com/file/p19846425/settings.xml settings.xml
>> http://www.nabble.com/file/p19846425/pom.xml pom.xml
>>
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-use-Maven-with-multiple-repositories--tp19846425p19846425.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> 
> -- 
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-use-Maven-with-multiple-repositories--tp19846425p19881419.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

[OT somewhat] commit modules separately or all under one project?

[Rick]

In a typical JEE project I have a parent module that my children all
inherit from. My modules look like:

parent
   ear
   ejb
   web
   jar

My debate is how to best put this into version control? Do most of you
commit the parent directory that holds all the submodules as 'one
project' or do some of you like to commit each module separately? I'm
leaning towards just checking in the whole parent directory as one
project, since the modules are all so closely related. Although the
jar file (Which is mostly util stuff can really be stand alone I
suppose and in theory the ejb module could be used by another web
project, but that's extremely unlikely.  )

-- 
Rick

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

Re: zip instead of jar

[buters]

Thank you, Oliver, very much.

I will try this and report my results hier later.

Best Regards, buters


Olivier Lamy wrote:
> 
> Hi,
> Have a look at source here [1] it's in the sandbox.
> 
> --
> Olivier
> 
> [1]
> https://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-zip-plugin/
> 
> 2008/10/6 buters <[EMAIL PROTECTED]>:
>>
>> Hi all,
>>
>> how can I create a zip-Archive instead of jar-one with Maven?
>>
>> Thanks beforehand,
>> regards, butters.
>> --
>> View this message in context:
>> http://www.nabble.com/zip-instead-of-jar-tp19830308p19830308.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/zip-instead-of-jar-tp19830308p19881322.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Issue with jspc-maven-plugin - specifying uriroot

[nsgood]

I had the same problem, here is the solution.
This is the snippet from CompilationMojoSupport.groovy (jspc-2.0-alpha-3)
   // Setup defaults (complex, can't init from expression)
if (!sources) {
sources = new FileSet()
sources.directory = "${project.basedir}/src/main/webapp"
sources.includes = null
}
So, in order to overrride the default path you must specify:
  
org.codehaus.mojo.jspc
jspc-maven-plugin
...

  
${webapp.dir}  
  

  


S.Murali wrote:
> 
> I have now bit more detail as what the exact problem is :
> when I run a mvn -X  , the jscp args is printing wrong directory for
> -uriroot.  
> 
> [DEBUG] Jscp args: ["-uriroot",
> "/home/myuser1/codebase/sandbox/teams/team1/dev3/mymodule/src/main/webapp",
> "-d",
> 
> This is due the fact that I am having a non-mavenised directory structure,
> .  The uriroot need to be pointing to  mymodule/vfe.  I have configured
> warSourceDirectory and webXml to point to right place.  But I am not sure,
> how to make uriroot point to correct location.  Seems I am missing some
> configuration.  Pl. let know, if you have idea on this.
> 
> Thanks, Murali
> 
> 
> S.Murali wrote:
>> 
>> Hi, 
>> I using jspc-maven-plugin pre-compile my JSP in a war packaged module.  I
>> am using following plugin configuration
>> 
>> 
>> org.codehaus.mojo.jspc
>> jspc-maven-plugin
>> 
>> 
>> check-jsp-source
>> process-sources
>> 
>>  compile
>> 
>> 
>> 
>> 
>> ../mymodule/vfe/WEB-INF/web.xml
>> ../mymodule/vfe
>> 
>> 
>> 
>> 
>> 
>> org.codehaus.mojo.jspc
>> jspc-compiler-tomcat6
>> 2.0-SNAPSHOT
>>  
>> 
>> 
>> 
>> 
>> org.apache.maven.plugins
>> maven-war-plugin
>> 
>> ../ventweb/target/jspweb.xml
>> 
>> 
>> 
>> On building module, I am getting following exception. 
>> 
>> [INFO] Compiling JSP source files to
>> /home/dev1/codebase/sandbox/teams/work/dev3/mymodule/target/jsp-source
>> [INFO]
>> 
>> [ERROR] FATAL ERROR
>> [INFO]
>> 
>> [INFO] The -uriroot option must specify a pre-existing directory
>> [INFO]
>> 
>> [INFO] Trace
>> org.apache.jasper.JasperException: The -uriroot option must specify a
>> pre-existing directory
>> at org.apache.jasper.JspC.execute(JspC.java:1128)
>> at
>> org.codehaus.mojo.jspc.compiler.tomcat6.JspCompilerImpl.compile(JspCompilerImpl.java:109)
>> 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.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(ReflectionMetaMethod.java:52)
>> at
>> org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassHelper.java:714)
>> at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:583)
>> at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:476)
>> at
>> org.codehaus.groovy.runtime.Invoker.invokePojoMethod(Invoker.java:104)
>> at
>> org.codehaus.groovy.runtime.Invoker.invokeMethod(Invoker.java:77)
>> at
>> org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:85)
>> at
>> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodN(ScriptBytecodeAdapter.java:158)
>> at
>> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethod0(ScriptBytecodeAdapter.java:182)
>> at
>> org.codehaus.mojo.jspc.CompilationMojoSupport.execute(CompilationMojoSupport.groovy:333)
>> 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

Re: Ant Tasks for Maven on Windows Error

[Andrew Ochsner]

Yeah so found the fix.

I had just specified the "url" attribute in the  task.
So, I added the "id" attribute and it worked just fine.

Hopefully this helps others in the future
Andy O

On Tue, Oct 7, 2008 at 11:33 PM, Brett Porter <[EMAIL PROTECTED]>wrote:

> it looks like the repository ID being used is incorrect. There should
> be a short, textual identifier, and then the full URL is the one given
> above. It seems the URL has been duplicated in your case.
>
> - Brett
>
> 2008/10/8 Andrew Ochsner <[EMAIL PROTECTED]>:
> > Hi:
> >
> > I am trying to add Spring (as an example) as a dependency using Ant Tasks
> > for Maven (inlining in the Ant build.xml).  I've been able to do this
> > without any problems w/ other dependencies.  Here's the error I get:
> >
> > runtime-dependencies:
> > [artifact:dependencies] [INFO] artifact org.springframework:spring-core:
> > checking for updates from http://download.java.net/maven/2/
> > [artifact:dependencies] An error has occurred while processing the Maven
> > artifact tasks.
> > [artifact:dependencies]  Diagnosis:
> > [artifact:dependencies]
> > [artifact:dependencies] Unable to resolve artifact: Unable to get
> dependency
> > information: Unable to store local copy of metadata: Error updating group
> > repository metadata
> > [artifact:dependencies]   org.springframework:spring-core:jar:null
> > [artifact:dependencies]
> > [artifact:dependencies] from the specified remote repositories:
> > [artifact:dependencies]   central (http://repo1.maven.org/maven2),
> > [artifact:dependencies]   http://download.java.net/maven/2/ (
> > http://download.java.net/maven/2/),
> > [artifact:dependencies]   http://maven.restlet.org/ (
> > http://maven.restlet.org/),
> > [artifact:dependencies]   http://repo1.maven.org/maven2/ (
> > http://repo1.maven.org/maven2/),
> > [artifact:dependencies]   maven2-repository.dev.java.net (
> > http://download.java.net/maven/2/)
> > [artifact:dependencies] Path to dependency:
> > [artifact:dependencies] 1) org.apache.maven:super-pom:jar:2.0
> > [artifact:dependencies] 2) com.sun.jersey:jersey-spring:jar:0.9-ea
> > [artifact:dependencies]
> > [artifact:dependencies]
> > [artifact:dependencies] C:\Documents and
> >
> Settings\aochsner\.m2\repository\org\springframework\spring-core\maven-metadata-http:\
> > download.java.net\maven\2\.xml (The filename, directory name, or volume
> > label syntax is incorrect)
> > [artifact:dependencies]
> >
> > BUILD FAILED
> > D:\Work\ribbit\ribbit\build.xml:75: Unable to resolve artifact: Unable to
> > get dependency information: Unable to store local copy of metadata: Error
> > updating group repository metadata
> >  org.springframework:spring-core:jar:null
> >
> > from the specified remote repositories:
> >  central (http://repo1.maven.org/maven2),
> >  http://download.java.net/maven/2/ (http://download.java.net/maven/2/),
> >  http://maven.restlet.org/ (http://maven.restlet.org/),
> >  http://repo1.maven.org/maven2/ (http://repo1.maven.org/maven2/),
> >  maven2-repository.dev.java.net (http://download.java.net/maven/2/)
> > Path to dependency:
> >1) org.apache.maven:super-pom:jar:2.0
> >2) com.sun.jersey:jersey-spring:jar:0.9-ea
> >
> >
> > The errors seems to be that it tries to write to a directory w/ a colon
> ":"
> > in it which is not allowed in Windows.  This task works fine on *nix.
> >
> > Any suggestions as to how to fix this or should I file a bug?
> >
> > Andy O
> >
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Bind Maven Goal Execution to a Lifecycle

[陈思淼]

Maybe you need to define your own life cycle mapping .

2008/10/7 Shelley <[EMAIL PROTECTED]>

> Is there any way to bind a goal's execution not only to a lifecycle
> *phase*,
> but to limit the execution to a specific *lifecycle *as well?
>
> I would like to bind a goal to the integration-test phase of the standard
> build lifecycle, but exclude it from being executed in a forked lifecycle
> (clover).  Is there any way to do this, or to detect which lifecycle is
> currently executing (so that a profile, for example, might be configured
> appropriately)?
>

Re: maven repository update.

[Mark H. Wood]

What the new user is missing is that the concept "up-to-date" is
overloaded and means very different things depending on whether it is
applied to a snapshot or to a release.

To make a long story short: if a released package needed repair then
the repaired version needed a new version number.  This is well known
to be good practice since long before Maven came along, even though we
all know of cases where someone got away with ignoring it.  The
correct response, upon noticing that two package release copies of equal
version number differ, is not "I'd better update" but "this is WRONG,
sound the alarm!"

The -help blurb could perhaps be improved by distinguishing between
"updated snapshot" and "higher release version" to show that the
concepts are different.  It would at least prompt some of us to
wonder, "what's different about these," and maybe go find out.

As a newbie myself, I often find that the Maven documentation assumes
far too much knowledge of the celebrated conventions and contains too
few pointers to them for the uninitiated.  That's why I bought the
book.  Yes, I will try to remember to report specific cases when I see
them.

-- 
Mark H. Wood, Lead System Programmer   [EMAIL PROTECTED]
Typically when a software vendor says that a product is "intuitive" he
means the exact opposite.



pgpoDq4zfbsxF.pgp
Description: PGP signature

Re: Problem moving property file around

[Jon Strayer]

On Tue, Oct 7, 2008 at 9:36 AM, Jon Strayer <[EMAIL PROTECTED]> wrote:
> Well, the configuration I have for the scm plugin didn't work:
> 
>org.apache.maven.plugins
>maven-scm-plugin
>
>developerConnection
>
>
>
>tag
>
>tag
>
>
> value="src/com/fusionsoftllc/achilles/client/BuildProperties.properties"/>
>
>
>
> 
>
> It still tried to tag the file.
>
> I want it in CVS because the default value (used in Eclipse builds) is
> there.  The surprise I'm worried about is someone changing the file
> and not seeing the change.
>
> On Mon, Oct 6, 2008 at 8:08 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
>> I don't quite get it... it sounds like you don't want the properties
>> file in CVS at all, so the solution you have at the end is fine. What
>> are the surprises you are concerned about?
>>
>> - Brett
>>
>> 2008/10/7 Jon Strayer <[EMAIL PROTECTED]>:
>>> Hang with me, this takes a while to explain.  :-)
>>>
>>> I'm trying to add a build number to a footer panel in GWT.
>>>
>>> CruiseControl passes the build label to Maven.
>>> Maven copies a properties file while performing a substitution which
>>> gives me a properties file in target/classes with the correct values
>>> in it.
>>> To get GWT to build the properties file into the application I have to
>>> copy the file from target/classes to the source tree (I use an ant
>>> task for that).
>>> For Eclipse builds to build correctly I need a default properties file
>>> in the source tree.
>>>
>>> The problem is that CVS won't tag the build because now the properties
>>> file in the source tree is not in CVS.  I tried many ways to make a
>>> backup copy of the file in the source tree and copy it back, but I've
>>> never been able to find a phase to tie different copying calls to that
>>> only executes once.
>>>
>>> So, in short, what I need is a way to
>>>1. backup a properties file in the source directory before
>>> resources are processed.
>>>2. copy a processed properties file from target/classes to the
>>> source tree after resources are processed.
>>>3. copy the backup of the properties file back to the source tree
>>> before scm:tag.
>>>
>>> Right now I'm trying to work around the problem by having scm:tag not
>>> tag that file, but that could lead to surprises.
>>>
>>> --
>>> Esse Quam Videre
>>> To Be, rather than to Seem
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>>
>> --
>> Brett Porter
>> Blog: http://blogs.exist.com/bporter/
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
>
> --
> Esse Quam Videre
> To Be, rather than to Seem
>


Does anyone understand why the above pom fragment doesn't keep scm:tag
from tagging the properties file?

-- 
Esse Quam Videre
To Be, rather than to Seem

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

Re: Dependency range resolution resolves to SNAPSHOTS!?

[Mark Hobson]

2008/10/8 Stefan Fritz <[EMAIL PROTECTED]>:
> Hi all,
>
> We recently (during the last weeks) ran into a situation where version
> ranges (e.g. [1.0,) ) where resolved to SNAPSHOT  versions as well.
> My understanding was always that if I specify a non-snapshot version in a
> range that only released version will be resolved.
>
> Is my understanding incorrect or is there a bug in dependency resolution?
>
> I'm using 2.0.9

This is indeed a bug, see:

http://jira.codehaus.org/browse/MNG-3092

Mark

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

Dependency range resolution resolves to SNAPSHOTS!?

[Stefan Fritz]

Hi all,

We recently (during the last weeks) ran into a situation where version 
ranges (e.g. [1.0,) ) where resolved to SNAPSHOT  versions as well.
My understanding was always that if I specify a non-snapshot version in 
a range that only released version will be resolved.


Is my understanding incorrect or is there a bug in dependency resolution?

I'm using 2.0.9

Thanks
Stefan


PS: Sorry if this has already discussed during the last weeks but 
couldn't find it in the archives


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

[EclipsePlugin] downloading sources without writing .project and .classpath files

[Andreas Riedel]

Hello List.

I've a question by using the Eclipse Plugin.
We will dispose the Q4E Eclipse Plugin.

So call the Plugin with:
mvn eclipse:eclipse -DdownloadSources=true

works fine.

But the writen .project and .classpath files are shared by SVN. So the other 
developer aren't beholden to run write the .project and .classpath files new.
So, is it possible to download the sources by the plugin but don't write the 
.project and .classpath files again and again.

TIA
Andreas




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

Re: evaluation report-history tools (e.g. xradar, sonar)

[aldana]

OK, thanks. Will give a try, though the last publish date (Sept. 2006)
doesn't look that project is maintained.



Michael McCallum-3 wrote:
> 
>  no experience but from having looked at
> the 
> projects they all follow a similar flawed approach... store the results of 
> runs in a database somewhere
> 
> the tools are good according to people i know who have used them...
> 
> On Wed, 08 Oct 2008 10:52:41 aldana wrote:
>> hi,
>>
>> we need some historic tracking for metrics. for that i considered using
>> http://sonar.codehaus.org/ and
>> http://xradar.sourceforge.net/issue-tracking.html. before doing an
>> evaluation, has anybody had good/bad experience with these products?
>>
>> or can you recommend any other similar tool?
>>
>> thanks.
>>
>> -
>> manuel aldana
>> aldana((at))gmx.de
>> software-engineering blog: http://www.aldana-online.de
> 
> 
> 
> -- 
> Michael McCallum
> Enterprise Engineer
> mailto:[EMAIL PROTECTED]
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 


-
manuel aldana
aldana((at))gmx.de
software-engineering blog: http://www.aldana-online.de
-- 
View this message in context: 
http://www.nabble.com/evaluation-report-history-tools-%28e.g.-xradar%2C-sonar%29-tp19868127p19876559.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Maven SCM (CVS) usage

[Marvin Froeder]

Ok, I will use cvs_native.

Thanks guys.


VELO

On Wed, Oct 8, 2008 at 5:37 AM, Emmanuel Venisse <[EMAIL PROTECTED]
> wrote:

> Hi Velo,
> By default, maven-scm use a pure java cvs client (a netbeans
> implementation) and the "auto-login" feature doesn't work well with external
> tool.
> By using the native cvs client, you use the command line, so if you already
> log in to a cvs server, all works fine like a direct cvs client command.
>
> Emmanuel
>
>
> On Wed, Oct 8, 2008 at 2:11 AM, Marvin Froeder <[EMAIL PROTECTED]> wrote:
>
>> Yes, and if I add
>>
>> -Dmaven.scm.provider.cvs.implementation=cvs_native
>>
>>
>> It works.
>>
>> Any thoughts?
>>
>>
>> VELO
>>
>> On Tue, Oct 7, 2008 at 8:50 PM, Brett Porter <[EMAIL PROTECTED]>
>> wrote:
>>
>> > Are you able to run other cvs commands from the command line? Is your
>> > home directory set consistently?
>> >
>> > 2008/10/8 Marvin Froeder <[EMAIL PROTECTED]>:
>> > > Hi folks,
>> > >
>> > > I'm using maven SCM to develop a maven plugin.
>> > >
>> > > And I got this exception:
>> > > org.apache.maven.scm.ScmException: password is required. You must run
>> a
>> > 'cvs
>> > > -d :pserver:[EMAIL PROTECTED]:2401/cvsroot/eclipse login'
>> first
>> > or
>> > > provide it in the connection url.
>> > >at
>> > >
>> >
>> org.apache.maven.scm.provider.cvslib.command.login.CvsPass.execute(CvsPass.java:136)
>> > >at
>> > >
>> >
>> org.apache.maven.scm.provider.cvslib.command.login.CvsLoginCommand.executeLoginCommand(CvsLoginCommand.java:66)
>> > >at
>> > >
>> >
>> org.apache.maven.scm.command.login.AbstractLoginCommand.executeCommand(AbstractLoginCommand.java:47)
>> > >at
>> > >
>> >
>> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58)
>> > >... 27 more
>> > >
>> > >
>> > > So I install tortoise CVS (to get cvs.exe at windows) and run:
>> > >
>> > > D:\temp>cvs -d :
>> pserver:[EMAIL PROTECTED]:2401/cvsroot/eclipselogin
>> > >> Logging in to :pserver:[EMAIL PROTECTED]:2401
>> :/cvsroot/eclipse
>> > >> CVS Password:
>> > >>
>> > >> D:\temp>
>> > >>
>> > >
>> > > So far so good.
>> > >
>> > > But, when I run maven again I got the same exception.  Does anyone
>> know
>> > what
>> > > is happening?
>> > >
>> > >
>> > > VELO
>> > >
>> >
>> >
>> >
>> > --
>> > Brett Porter
>> > Blog: http://blogs.exist.com/bporter/
>> >
>>
>
>

Custom locations with maven-scm-plugin (SVN)

[Olivier Gies]

Hi everyone,

I am trying to structure a complex Maven structure for a 
multi-module-multi-projects delivery chain, based on a set of Subversion 
repositories.


I have been browsing around the maven-scm-plugin configuration and 
usage, but could not solve this simple problem:


- how to define a custom "checkout" location ? I don't (necessarily) 
want the pom.xml to be located in the Subversion repository configured 
under the , nor do I want this repository to be checked-out right 
under the current working directory...


- IF this is done in the $user.home/.scm/???-settings.xml, how can I 
instruct Maven to actually look into another place for this file ? (i.e. 
the purpose is to have different checkout locations for different projects)


Any help appreciated!
Thanks
Olivier

--

*Olivier Gies*

*Delivery Manager
Customs & Tax Software Engineering Center
Bull, Architect of an Open World ^TM
Phone: +86 (10) 65978001 - Ext 555 *

*www.bull.com *

*This e-mail contains material that is confidential for the sole use of 
the intended recipient. Any review, reliance or distribution by others 
or forwarding without express permission is strictly prohibited. If you 
are not the intended recipient, please contact the sender and delete all 
copies.*

[ANN] Maven Filtering 1.0-beta-2 Released

[Olivier Lamy]

The Maven team is pleased to announce the release of the Maven
Filtering, version 1.0-beta-2.

These Plexus components have been built from the filtering
process/code in Maven Resources Plugin. The goal is to provide a
shared component for all plugins which needs to filter resources.

http://maven.apache.org/shared/maven-filtering/


Release Notes - Maven Shared Components - Version maven-filtering-1.0-beta-2


** Bug
* [MSHARED-60] - Filtering ${foo.file} evaluates to in full path to pom.xml

** Improvement
* [MSHARED-51] - ability to escape interpolation with \
* [MSHARED-66] - targetPath doesn't accept absolute paths
* [MSHARED-67] - Add a parameter to force overwrite existing files
even if the destination files are newer
* [MSHARED-68] - Parameter to copy empty directory.

** Wish
* [MSHARED-59] - More debug output in maven filtering


Have Fun,

-The Maven team

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

dynamic addition of dependencies

[Wolfgang.Winter]

Hi,

In a plugin I want to dynamically check the dependencies and resolve
(download) correspondent artifacts with another classifier. Example: in
pom is declared dependency core-translation-0.2. The plugin should
download automatically core-translation-0.2-install. 

 

My idea:

Loop through the dependencies and create for each a new Artifact with
ArtifactFactory.createDependencyArtifact(). Download the artifact with
ArtifactResolver.resolve(...) 

Is this a correct approach?

 

Problems:

1.  in the dependencies list injected with ${project.dependencies}
only partly transitive dependencies are listed, they are not completely
resolved. In the example the dependencies of  core-translation-0.2 are
missing. However, I declared the mojo with @requiresDependencyResolution
compile 
2.  The ArtifactResolver.resolve() method needs the remote and local
repositories as parameter. The remote I can get from MavenProject but
from where do I get the local repository?

 

 

Kind regards

Wolfgang 

 

Re: Mac OS 10.5.5: mvn release:prepare fails with Exec format error

[Marcus Linke]

OK, i've found the reason now. The 'mvn' command was wrapped by a shell
script that sets JAVA_HOME to a Java 1.4 environment. This was done by a
mate of me, so i had no clue. After removing this all works fine. Sorry,
but if someone runs into the same error this post may help.

Regards 

Marcus


"Maven Users List"  writes:
>Hello,
>
>if i run the release:prepare goal on Mac OS 10.5.5 maven aborts with the
>following error message.
>is this a bug or a case of misconfiguration? What can i do. Please help!
>
>Regards 
>
>Marcus
>
>mvn -e -DdryRun=true release:prepare
>own maven starter
>+ Error stacktraces are turned on.
>[INFO] Scanning for projects...
>[INFO] Searching repository for plugin with prefix: 'release'.
>[INFO]
>
>[INFO] Building devel-tools
>[INFO]task-segment: [release:prepare] (aggregator-style)
>[INFO]
>
>[INFO] [release:prepare]
>[INFO] Resuming release from phase 'run-preparation-goals'
>[INFO] Executing preparation goals - since this is simulation mode it is
>running against the original project, not the rewritten ones
>[INFO] Executing goals 'clean verify'...
>[INFO] Executing: mvn clean verify --no-plugin-updates -P
>development,sonar,sonar
>Java: UNIXProcess:forkAndExec: exec failed: Exec format error
>[INFO]
>
>[ERROR] BUILD ERROR
>[INFO]
>
>[INFO] Maven execution failed, exit code: '-1'
>
>[INFO]
>
>[INFO] Trace
>org.apache.maven.lifecycle.LifecycleExecutionException: Maven execution
>failed, exit code: '-1'
>   at
>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
>   at
>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>   at
>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>   at
>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>   at
>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
>   at
>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>   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:324)
>   at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>Caused by: org.apache.maven.plugin.MojoExecutionException: Maven execution
>failed, exit code: '-1'
>   at
>org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:140)
>   at
>org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>   at
>org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>   ... 16 more
>Caused by: org.apache.maven.shared.release.ReleaseExecutionException:
>Maven execution failed, exit code: '-1'
>   at
>org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:66)
>   at
>org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:42)
>   at
>org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.simulate(RunPrepareGoalsPhase.java:54)
>   at
>org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:190)
>   at
>org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131)
>   at
>org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94)
>   at
>org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:136)
>   ... 18 more
>Caused by: org.apache.maven.shared.release.exec.MavenExecutorException:
>Maven execution failed, exit code: '-1'
>   at
>org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:108)
>   at
>org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.ja

Re: LATEST version

[Brett Porter]

Well, it's really not intended for that purpose, particularly because
of the reproducibility problems it will incur. However, adding the
plugin metadata goal to your build should do this if you choose that
path.

- Brett

2008/10/8 Jeff MAURY <[EMAIL PROTECTED]>:
> On Wed, Oct 8, 2008 at 10:39 AM, Brett Porter <[EMAIL PROTECTED]>wrote:
>
>> This is done specifically for plugins by a special binding in the
>> lifecycle. You'd need to do likewise for your artifacts as they are
>> deployed, or modify the repository metadata.
>
> Is there an existing Maven plugin to do so ?
>
> Jeff MAURY
>
>>
>>
>> - Brett
>>
>> 2008/10/8 Jeff MAURY <[EMAIL PROTECTED]>:
>> > Hello,
>> >
>> > I'm facing an issue with the LATEST version. I can't make it work. If I
>> > install or deploy a snapshot artifact, and then use this dependency with
>> the
>> > LATEST version identifier, then this dependency is never resolved by
>> Maven.
>> > I was able to make to work for RELEASE with the updateReleaseInfo for non
>> > snapshots artifacts.
>> > It seems that the latest flag must be present in the repository metadata
>> but
>> > I can't find how Maven will generate this info. It is done for Maven
>> plugins
>> > but how to do it for non Maven plugins artifacts ?
>> >
>> > Regards
>> > Jeff MAURY
>> >
>> > --
>> > La mélancolie c'est communiste
>> > Tout le monde y a droit de temps en temps
>> > La mélancolie n'est pas capitaliste
>> > C'est même gratuit pour les perdants
>> > La mélancolie c'est pacifiste
>> > On ne lui rentre jamais dedans
>> > La mélancolie oh tu sais ça existe
>> > Elle se prend même avec des gants
>> > La mélancolie c'est pour les syndicalistes
>> > Il faut juste sa carte de permanent
>> >
>> > Miossec (2006)
>> >
>> > http://www.jeffmaury.com
>> > http://riadiscuss.jeffmaury.com
>> > http://www.lastfm.fr/listen/user/jeffmaury/personal
>> > Mes CDs à récupérer:
>> > http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTA&hl=en
>> >
>>
>>
>>
>> --
>> Brett Porter
>> Blog: http://blogs.exist.com/bporter/
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.lastfm.fr/listen/user/jeffmaury/personal
> Mes CDs à récupérer:
> http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTA&hl=en
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

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

Assemply for EAR project including dependencies and sources

[Baeriswyl Kuno - Extern (IT-BA-MV)]

Hello,

I use the maven-source-plugin in each project. For each artifact it creates 
another artifact with the sources classifier including the project sources. 
Like for myartifact.jar it would generate an artifact myartifact-sources.jar

Now, I want to create an assemply for an EAR Project including all 
dependenciens and it's source archives created like mentioned above.
I'd like to create something like
  myear-src.zip
  |
 +  -- myartifact.jar
 +  -- myartifact-sources.jar

Using the assemply this would be done like this :


  src
  
zip
  
  

  
  *:war:*
  *:jar:*
  *:sources
  

  


Unfortunately, this works only if I define each sources artifact as a 
dependency of my EAR project.  Otherwise I'll get following warning:

[WARNING] The following patterns were never triggered in this artifact 
inclusion filter:
o  '*:sources'

Futhermore, I don't know which scope I should give to such a dependency.

Is there a better way to create such an archive with sources?

Thanks

Kuno

Re: LATEST version

[Jeff MAURY]

On Wed, Oct 8, 2008 at 10:39 AM, Brett Porter <[EMAIL PROTECTED]>wrote:

> This is done specifically for plugins by a special binding in the
> lifecycle. You'd need to do likewise for your artifacts as they are
> deployed, or modify the repository metadata.

Is there an existing Maven plugin to do so ?

Jeff MAURY

>
>
> - Brett
>
> 2008/10/8 Jeff MAURY <[EMAIL PROTECTED]>:
> > Hello,
> >
> > I'm facing an issue with the LATEST version. I can't make it work. If I
> > install or deploy a snapshot artifact, and then use this dependency with
> the
> > LATEST version identifier, then this dependency is never resolved by
> Maven.
> > I was able to make to work for RELEASE with the updateReleaseInfo for non
> > snapshots artifacts.
> > It seems that the latest flag must be present in the repository metadata
> but
> > I can't find how Maven will generate this info. It is done for Maven
> plugins
> > but how to do it for non Maven plugins artifacts ?
> >
> > Regards
> > Jeff MAURY
> >
> > --
> > La mélancolie c'est communiste
> > Tout le monde y a droit de temps en temps
> > La mélancolie n'est pas capitaliste
> > C'est même gratuit pour les perdants
> > La mélancolie c'est pacifiste
> > On ne lui rentre jamais dedans
> > La mélancolie oh tu sais ça existe
> > Elle se prend même avec des gants
> > La mélancolie c'est pour les syndicalistes
> > Il faut juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> > http://www.lastfm.fr/listen/user/jeffmaury/personal
> > Mes CDs à récupérer:
> > http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTA&hl=en
> >
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.lastfm.fr/listen/user/jeffmaury/personal
Mes CDs à récupérer:
http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTA&hl=en

Re: LATEST version

[Brett Porter]

This is done specifically for plugins by a special binding in the
lifecycle. You'd need to do likewise for your artifacts as they are
deployed, or modify the repository metadata.

- Brett

2008/10/8 Jeff MAURY <[EMAIL PROTECTED]>:
> Hello,
>
> I'm facing an issue with the LATEST version. I can't make it work. If I
> install or deploy a snapshot artifact, and then use this dependency with the
> LATEST version identifier, then this dependency is never resolved by Maven.
> I was able to make to work for RELEASE with the updateReleaseInfo for non
> snapshots artifacts.
> It seems that the latest flag must be present in the repository metadata but
> I can't find how Maven will generate this info. It is done for Maven plugins
> but how to do it for non Maven plugins artifacts ?
>
> Regards
> Jeff MAURY
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.lastfm.fr/listen/user/jeffmaury/personal
> Mes CDs à récupérer:
> http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTA&hl=en
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

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

Re: Maven SCM (CVS) usage

[Emmanuel Venisse]

Hi Velo,
By default, maven-scm use a pure java cvs client (a netbeans implementation)
and the "auto-login" feature doesn't work well with external tool.
By using the native cvs client, you use the command line, so if you already
log in to a cvs server, all works fine like a direct cvs client command.

Emmanuel

On Wed, Oct 8, 2008 at 2:11 AM, Marvin Froeder <[EMAIL PROTECTED]> wrote:

> Yes, and if I add
>
> -Dmaven.scm.provider.cvs.implementation=cvs_native
>
>
> It works.
>
> Any thoughts?
>
>
> VELO
>
> On Tue, Oct 7, 2008 at 8:50 PM, Brett Porter <[EMAIL PROTECTED]>
> wrote:
>
> > Are you able to run other cvs commands from the command line? Is your
> > home directory set consistently?
> >
> > 2008/10/8 Marvin Froeder <[EMAIL PROTECTED]>:
> > > Hi folks,
> > >
> > > I'm using maven SCM to develop a maven plugin.
> > >
> > > And I got this exception:
> > > org.apache.maven.scm.ScmException: password is required. You must run a
> > 'cvs
> > > -d :pserver:[EMAIL PROTECTED]:2401/cvsroot/eclipse login'
> first
> > or
> > > provide it in the connection url.
> > >at
> > >
> >
> org.apache.maven.scm.provider.cvslib.command.login.CvsPass.execute(CvsPass.java:136)
> > >at
> > >
> >
> org.apache.maven.scm.provider.cvslib.command.login.CvsLoginCommand.executeLoginCommand(CvsLoginCommand.java:66)
> > >at
> > >
> >
> org.apache.maven.scm.command.login.AbstractLoginCommand.executeCommand(AbstractLoginCommand.java:47)
> > >at
> > >
> >
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58)
> > >... 27 more
> > >
> > >
> > > So I install tortoise CVS (to get cvs.exe at windows) and run:
> > >
> > > D:\temp>cvs -d :
> pserver:[EMAIL PROTECTED]:2401/cvsroot/eclipselogin
> > >> Logging in to :pserver:[EMAIL PROTECTED]:2401
> :/cvsroot/eclipse
> > >> CVS Password:
> > >>
> > >> D:\temp>
> > >>
> > >
> > > So far so good.
> > >
> > > But, when I run maven again I got the same exception.  Does anyone know
> > what
> > > is happening?
> > >
> > >
> > > VELO
> > >
> >
> >
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
> >
>

LATEST version

[Jeff MAURY]

Hello,

I'm facing an issue with the LATEST version. I can't make it work. If I
install or deploy a snapshot artifact, and then use this dependency with the
LATEST version identifier, then this dependency is never resolved by Maven.
I was able to make to work for RELEASE with the updateReleaseInfo for non
snapshots artifacts.
It seems that the latest flag must be present in the repository metadata but
I can't find how Maven will generate this info. It is done for Maven plugins
but how to do it for non Maven plugins artifacts ?

Regards
Jeff MAURY

-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.lastfm.fr/listen/user/jeffmaury/personal
Mes CDs à récupérer:
http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTA&hl=en

Mac OS 10.5.5: mvn release:prepare fails with Exec format error

[Marcus Linke]

Hello,

if i run the release:prepare goal on Mac OS 10.5.5 maven aborts with the
following error message.
is this a bug or a case of misconfiguration? What can i do. Please help!

Regards 

Marcus

mvn -e -DdryRun=true release:prepare
own maven starter
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO]

[INFO] Building devel-tools
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO]

[INFO] [release:prepare]
[INFO] Resuming release from phase 'run-preparation-goals'
[INFO] Executing preparation goals - since this is simulation mode it is
running against the original project, not the rewritten ones
[INFO] Executing goals 'clean verify'...
[INFO] Executing: mvn clean verify --no-plugin-updates -P
development,sonar,sonar
Java: UNIXProcess:forkAndExec: exec failed: Exec format error
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Maven execution failed, exit code: '-1'

[INFO]

[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Maven execution
failed, exit code: '-1'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Maven execution
failed, exit code: '-1'
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:140)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.apache.maven.shared.release.ReleaseExecutionException:
Maven execution failed, exit code: '-1'
at
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:66)
at
org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:42)
at
org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.simulate(RunPrepareGoalsPhase.java:54)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:190)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:136)
... 18 more
Caused by: org.apache.maven.shared.release.exec.MavenExecutorException:
Maven execution failed, exit code: '-1'
at
org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:108)
at
org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:126)
at
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:59)
... 24 more
[INFO]

[INFO] Total time: 3 seconds
[INFO] Finished at: Wed Oct 08 10:12:38 CEST 2008
[INFO] Final Memory: 6M/11M
[INFO]
-

Re: What's the defference between the dependencyManagement and dependencies?

[陈思淼]

I think the dependencyManagement mechanism is Less usefull,because when the
transitive dependency conflict. In some case, It need strict function
and pressure test to decide which version to use.
and the SCM should control the authority to decide which version to override
another depends on the test result. so the config should not be define in
the pom.xml.


2008/10/8 Stephen Connolly <[EMAIL PROTECTED]>

> OK, I'll start back a piece from your question.
>
> When you do
>
> 
>  ...
>  a
>  ...
>  
>  
>foo
>bar
> 1.0
>  
>  ...
>  
>   ...
> 
>
> what you are doing is telling maven that your project a needs foo:bar
> and would, if its opinion counts, prefer to use version 1.0
>
> If I have another project with
>
> 
>  ...
>  b
>  ...
>  
>  
>foo
>bar
>2.0
>  
>  ...
>  
>  ...
> 
>
> If project c lists a & b as it's dependencies, which version of
> foo:bar will maven use?
>
> a would prefer 1.0
> b would prefer 2.0
>
> There are rules which allow Maven to deterministically figure this out
> (in this case the first dependency listed in project c will win,
> unless c depends on foo:bar directly itself)
>
> so for
>
> 
>  ...
>  c
>  ...
>  
>  
>...
>b
>...
>  
>  
>...
>a
>...
>  
>  ...
>  
>  ...
> 
>
> c will end up using version 2.0.
>
> The dependencyManagement is a way of more strongly hinting to maven
> that it should use a specific version...
>
> so since c does not directly depend on foo:bar, we don't really want
> to add foo:bar as a dependency of project c.
>
> By adding it as a dependencyManagement we can tell maven, oh by the
> way, if you see this dependency, i'd really really like it if you can
> use this version.
>
> The other use case for dependencyManagement is to put it in a parent
> pom... that way all the parent's children do not have to keep
> specifying the version... in fact they can safely omit the version
>
> -Stephen
>
> 2008/10/8 Wayne Fay <[EMAIL PROTECTED]>:
> > Primarily,  does not actually attach an artifact
> > dependency to a given project, while declaring a  does
> > exactly that.
> >
> > So you could have a project with 10 items in depMgmt and no deps which
> > tells users (and Maven) that it can be built all on its own.
> >
> > Wayne
> >
> > 2008/10/8 陈思淼 <[EMAIL PROTECTED]>:
> >>  
> >>
> >>  
> >>test
> >>d
> >>1.0
> >>  
> >>
> >>  
> >>
> >>
> >>
> >>  maven-test
> >>  c
> >>  runtime
> >>
> >>  
> >>
> >
>

Re: Add directory to the classpath

[Jeff MAURY]

In the Maven way of life, the classpath is managed through the dependencies
mecanism. So I would say no.
Regarding you case, I think this is a problem regarding the way you run
JBoss with Maven. So you should look at the cargo maven plugin or, but I
don't know if such a plugin exists, the JBoss maven plugin.

Regards
Jeff MAURY

On Wed, Oct 8, 2008 at 8:27 AM, Thomas Jonsson <[EMAIL PROTECTED]>wrote:

> Hi!
>
> Is it possible to add a directory to the classpath with maven? To make
> the directory as a jar artifact is not an option.
> The background is that I'm managing a seam project using maven, and in
> the test phase, a "bootstrap directory" must be on the classpath ,
> otherwise the jboss embedded application server can't start. Any
> ideas?
>
> Best regards,
> Thomas
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.lastfm.fr/listen/user/jeffmaury/personal
Mes CDs à récupérer:
http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTA&hl=en

Add directory to the classpath

[Thomas Jonsson]

Hi!

Is it possible to add a directory to the classpath with maven? To make
the directory as a jar artifact is not an option.
The background is that I'm managing a seam project using maven, and in
the test phase, a "bootstrap directory" must be on the classpath ,
otherwise the jboss embedded application server can't start. Any
ideas?

Best regards,
Thomas

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

Re: Installing a checked-out JAR, not the packaged one

[Heinrich Nirschl]

On Tue, Oct 7, 2008 at 9:25 PM, Michael Hüttermann
<[EMAIL PROTECTED]> wrote:
> Thanks! Isn't there any way to jump into the lifecycle and prevent Maven
> to deploy the packaged jar ?? Or: to prevent Maven to package the jar?
>

As far as I know, the "pom" lifecycle does not have plugins bound to
phases. So you could change the packaging type of the module to pom
and bind the plugins you want to run explicitly. You´ll probably have
to experiment a bit but I think it might work.

Btw. is this jar some sort of library (in that case it is better to
deploy it to a repository) or is it built by eclipse? In the latter
case you should consider to let maven compile the classes and assemble
the jar. This leads to more reproducible results.

Henry

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

Re: What's the defference between the dependencyManagement and dependencies?

[Stephen Connolly]

OK, I'll start back a piece from your question.

When you do


  ...
  a
  ...
  
  
foo
bar
1.0
  
  ...
  
  ...


what you are doing is telling maven that your project a needs foo:bar
and would, if its opinion counts, prefer to use version 1.0

If I have another project with


  ...
  b
  ...
  
  
foo
bar
2.0
  
  ...
  
  ...


If project c lists a & b as it's dependencies, which version of
foo:bar will maven use?

a would prefer 1.0
b would prefer 2.0

There are rules which allow Maven to deterministically figure this out
(in this case the first dependency listed in project c will win,
unless c depends on foo:bar directly itself)

so for


  ...
  c
  ...
  
  
...
b
...
  
  
...
a
...
  
  ...
  
  ...


c will end up using version 2.0.

The dependencyManagement is a way of more strongly hinting to maven
that it should use a specific version...

so since c does not directly depend on foo:bar, we don't really want
to add foo:bar as a dependency of project c.

By adding it as a dependencyManagement we can tell maven, oh by the
way, if you see this dependency, i'd really really like it if you can
use this version.

The other use case for dependencyManagement is to put it in a parent
pom... that way all the parent's children do not have to keep
specifying the version... in fact they can safely omit the version

-Stephen

2008/10/8 Wayne Fay <[EMAIL PROTECTED]>:
> Primarily,  does not actually attach an artifact
> dependency to a given project, while declaring a  does
> exactly that.
>
> So you could have a project with 10 items in depMgmt and no deps which
> tells users (and Maven) that it can be built all on its own.
>
> Wayne
>
> 2008/10/8 陈思淼 <[EMAIL PROTECTED]>:
>>  
>>
>>  
>>test
>>d
>>1.0
>>  
>>
>>  
>>
>>
>>
>>  maven-test
>>  c
>>  runtime
>>
>>  
>>
>

Re: where should I put my config file?

[Wayne Fay]

This is described in the documentation:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html

And here it is in the source code for the plugin:
http://maven.apache.org/plugins/maven-checkstyle-plugin/xref/org/apache/maven/plugin/checkstyle/CheckstyleReport.html#1127

Wayne

2008/10/7 陈思淼 <[EMAIL PROTECTED]>:
> can you give me a example?
>
> 2008/10/8 陈思淼 <[EMAIL PROTECTED]>
>
>> thanks for Brett 's advice. can you make it more specific? I'm Interesting
>> about you mention about：locate from the repository。
>> can you give me some example,how can I put the checktyle.xml in the
>> repository, and the plugin get it thought a URL。
>>
>> 2008/10/8 Brett Porter <[EMAIL PROTECTED]>
>>
>> I suggest looking at the Checkstyle plugin and similar for examples of
>>> how to do this. They tend to offer the option of:
>>> - built in (the example you gave)
>>> - download from an URL (for a single file)
>>> - locate from the repository (better since it makes it easy to
>>> relocate/manage)
>>>
>>> Cheers,
>>> Brett
>>>
>>> 2008/10/8 陈思淼 <[EMAIL PROTECTED]>:
>>> > I have write a plugin which read from a config some mapping information
>>> and
>>> > do some thing.Of cause I can put the config file into src/resources, but
>>> I
>>> > will and more and more mapping information into the config file. I dont
>>> want
>>> > to deploy the plugin artifact after I modify the config file. Can I put
>>> the
>>> > config file in some independent location where my own plugin can access
>>>  but
>>> > not contain in the src/resources, Is there any mechanism support this
>>> kind
>>> > of needs? do I need to write a new packaging type called config-file,
>>> and
>>> > deploy it to the repository?
>>> >
>>>
>>>
>>>
>>> --
>>> Brett Porter
>>> Blog: http://blogs.exist.com/bporter/
>>>
>>
>>
>

Re: What's the defference between the dependencyManagement and dependencies?

[Wayne Fay]

Primarily,  does not actually attach an artifact
dependency to a given project, while declaring a  does
exactly that.

So you could have a project with 10 items in depMgmt and no deps which
tells users (and Maven) that it can be built all on its own.

Wayne

2008/10/8 陈思淼 <[EMAIL PROTECTED]>:
>  
>
>  
>test
>d
>1.0
>  
>
>  
>
>
>  
>
>  maven-test
>  a
>  1.0
>  runtime
>
>
>  maven-test
>  c
>  runtime
>
>  
>

What's the defference between the dependencyManagement and dependencies?

[陈思淼]

 

  
test
d
1.0
  

  


  

  maven-test
  a
  1.0
  runtime


  maven-test
  c
  runtime