RE: parallel builds and failing for non @threadsafe mojos

[Nord, James]

OK,

I've scanned through what might be possible in the enforcer plugin but drew a 
blank.

I would need to get the plugin somehow from the plexus container from the 
session to get the mojos (based on the project and config) to inspect - but the 
session.getContainer() is deprecated with no apparent replacement.
What am I missing - or am I looking in the wrong area - or is this just not 
even available given a MavenProject and a MavenSession?

/James

-Original Message-
From: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] On 
Behalf Of Kristian Rosenvold
Sent: 15 November 2012 18:50
To: Maven Users List
Subject: Re: parallel builds and failing for non @threadsafe mojos

No

2012/11/15 Nord, James :
> Hi all,
>
> Is there any way to get Maven to abort the build (rather than spit out a 
> warning) if a parallel build is requested but a non threadsafe mojo is 
> encountered?
>
> /James
>
> 
>
>
> **
>  This message is confidential and intended only for 
> the addressee. If you have received this message in error, please immediately 
> notify the postmas...@nds.com and delete it from your system as well as any 
> copies. The content of e-mails as well as traffic data may be monitored by 
> NDS for employment and security purposes. To protect the environment please 
> do not print this e-mail unless necessary.
>
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, 
> TW18 4EX, United Kingdom. A company registered in England and Wales. 
> Registered no. 3080780. VAT no. GB 603 8808 40-00
> **
> 

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


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

parallel builds and failing for non @threadsafe mojos

[Nord, James]

Hi all,

Is there any way to get Maven to abort the build (rather than spit out a 
warning) if a parallel build is requested but a non threadsafe mojo is 
encountered?

/James




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: mvn release:prepare cannot git-commit the pom.xml change

[Nord, James]

Have you tried with the git windows port rather than Cygwin git.
That  works for me on windows with the release plugin.

Mixing windows and DOS paths / tools is never a good combination in my 
experience.

/James

-Original Message-
From: Martin Lichtin [mailto:lich...@yahoo.com]
Sent: 13 November 2012 15:50
To: Maven Users List
Subject: Re: mvn release:prepare cannot git-commit the pom.xml change

Same with version 2.3.2 (many thanks of course for pointing out the old version 
I was trying with).

[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
[INFO] Working directory: C:\users\mli\nuc\core\master\main\inuc
[INFO] Executing: cmd.exe /X /C "git status"
[INFO] Working directory: C:\users\mli\nuc\core\master\main\inuc
[INFO] Executing: cmd.exe /X /C "git commit --verbose -F 
C:\cygwin\tmp\maven-scm-915771020.commit pom.xml"
[INFO] Working directory: C:\users\mli\nuc\core\master\main\inuc
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 10.227s
[INFO] Finished at: Tue Nov 13 16:45:35 CET 2012 [INFO] Final Memory: 6M/102M 
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on 
project inuc: Unable to commit files [ERROR] Provider message:
[ERROR] The git-commit command failed.
[ERROR] Command output:
[ERROR] fatal: could not read log file 
'inuc/C:\cygwin\tmp\maven-scm-915771020.commit': No such file or directory

Strangely enough, it looks like a Git issue?

$ echo X > "C:\cygwin\tmp\commit"
$ cat "C:\cygwin\tmp\commit"
X
$ cmd.exe /X /C "git commit --verbose -F C:\cygwin\tmp\commit pom.xml"
fatal: could not read log file 'inuc/C:\cygwin\tmp\commit': No such file or 
directory


$ git --version
git version 1.7.9




>
> From: Robert Scholte 
>To: Maven Users List 
>Sent: Tuesday, November 13, 2012 3:55 PM
>Subject: Re: mvn release:prepare cannot git-commit the pom.xml change
>
>The logging says: "org.apache.maven.plugins:maven-release-plugin:2.0:prepare"
>This means you're using a pretty old version of the maven-release-plugin.
>Try to lock the version on 2.3.2 first.
>
>Robert
>
>
>Op Tue, 13 Nov 2012 15:17:33 +0100 schreef Martin Lichtin :
>
>> Hi
>> As a first-time user of the "release" plugin, I'm running into the following 
>> problem:
>>
>> [INFO] Checking in modified POMs...
>> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
>> [INFO] Working directory: C:\Users\mli\nuc\core\master\main\inuc
>> [INFO] Executing: cmd.exe /X /C "git status"
>> [INFO] Working directory: C:\Users\mli\nuc\core\master\main\inuc
>> [INFO] Executing: cmd.exe /X /C "git commit --verbose -F 
>> C:\cygwin\tmp\maven-scm-1106545469.commit pom.xml"
>> [INFO] Working directory: C:\Users\mli\nuc\core\master\main\inuc
>> [INFO]
>> -
>> ---
>> [INFO] BUILD FAILURE
>> [INFO]
>> -
>> ---
>> [INFO] Total time: 6.521s
>> [INFO] Finished at: Tue Nov 13 14:44:27 CET 2012 [INFO] Final Memory:
>> 7M/104M [INFO]
>> -
>> --- [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-release-plugin:2.0:prepare
>> (default-cli) on project inuc: Unable to commit files [ERROR] Provider 
>> message:
>> [ERROR] The git-commit command failed.
>> [ERROR] Command output:
>> [ERROR] fatal: could not read log file
>> 'inuc/C:\cygwin\tmp\maven-scm-1106545469.commit': No such file or
>> directory
>>
>> Note how the last line shows a log file name erroneously prefixed with the 
>> module name.
>> Is this a problem caused by cmd.exe versus cygwin interaction? Or could it 
>> even be a git bug.
>>
>> Martin
>
>-
>To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>For additional commands, e-mail: users-h...@maven.apache.org
>
>
>
>




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
*

RE: Maven 3 deployment authentication

[Nord, James]

> -Original Message-
> From: Thomas Broyer [mailto:t.bro...@gmail.com]
> Sent: 23 August 2012 15:44
> To: Maven Users List
> Subject: Re: Maven 3 deployment authentication
>
> On Thu, Aug 23, 2012 at 4:30 PM, Thomas Scheffler  jena.de> wrote:
> > Am 23.08.2012 12:38, schrieb Nord, James:
> >> Hi all,
> >>
> >> In Maven 3.0.4 and am seeing the following error when I try to release a
> project.
> >>
> >>
> >> [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @
> >> rpm-maven-plugin ---
> >>
> >> Uploading:
> >> http://myrepo/service/local/staging/deploy/maven2/org/codehaus/mojo/r
> >> pm-maven-plugin/2.1-alpha-2_NDS1/rpm-maven-plugin-2.1-alpha-
> 2_NDS1.ja
> >> r
> >>
> >> Uploading:
> >> http://myrepo/service/local/staging/deploy/maven2/org/codehaus/mojo/r
> >> pm-maven-plugin/2.1-alpha-2_NDS1/rpm-maven-plugin-2.1-alpha-
> 2_NDS1.po
> >> m
> >>
> >> Aug 23, 2012 10:40:47 AM
> >> org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultR
> >> equestDirector handleResponse
> >>
> >> WARNING: Authentication error: basic authorization challenge
> >> expected, but not found
> >
> > Hi,
> >
> > usually one would not allow basic authentication over unencrypted
> > channels like http. This provides no security and every hop in the
> > internet can gather login and passwords really simple.
> >
> > So probably you just change the "http:" to "https:" - if the server is
> > well configured or speak to the administrator of the repository on how
> > to transmit artifacts there.
>
> That's not the issue, as someone else has been having this same error with an
> https:// URL:
> http://java.net/jira/browse/MAVEN2_REPOSITORY-119
>
> Are the username and password configured in settings.xml for the
> distributionManagement server?
> http://maven.apache.org/plugins/maven-deploy-plugin/usage.html

I found the cause,
The user (which was configured in settings.xml correctly and serverIds matched) 
didn’t have sufficient access to the nexus staging area for this specific 
groupid.

Giving the user access for this groupid solves the issue, but this was a 
strange failure - I would have exected a 403..

(BTW - for the security paranoid I'm not sending plaintext passwords on the 
internet)

Thanks

/James




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

Maven 3 deployment authentication

[Nord, James]

Hi all,

In Maven 3.0.4 and am seeing the following error when I try to release a 
project.


[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ 
rpm-maven-plugin ---

Uploading: 
http://myrepo/service/local/staging/deploy/maven2/org/codehaus/mojo/rpm-maven-plugin/2.1-alpha-2_NDS1/rpm-maven-plugin-2.1-alpha-2_NDS1.jar

Uploading: 
http://myrepo/service/local/staging/deploy/maven2/org/codehaus/mojo/rpm-maven-plugin/2.1-alpha-2_NDS1/rpm-maven-plugin-2.1-alpha-2_NDS1.pom

Aug 23, 2012 10:40:47 AM 
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestDirector
 handleResponse

WARNING: Authentication error: basic authorization challenge expected, but 
not found

[INFO] 


[INFO] BUILD FAILURE

Aug 23, 2012 10:40:47 AM 
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestDirector
 handleResponse

WARNING: Authentication error: basic authorization challenge expected, but 
not found

[INFO] 


[INFO] Total time: 42.591s

[INFO] Finished at: Thu Aug 23 10:40:47 BST 2012

[INFO] Final Memory: 22M/602M

[INFO] 


[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on 
project rpm-maven-plugin: Failed to deploy artifacts: Could not transfer 
artifact org.codehaus.mojo:rpm-maven-plugin:jar:2.1-alpha-2_NDS1 from/to My 
Repository (http://myrepo/service/local/staging/deploy/maven2/): Failed to 
transfer file: 
http://myrepo/service/local/staging/deploy/maven2/org/codehaus/mojo/rpm-maven-plugin/2.1-alpha-2_NDS1/rpm-maven-plugin-2.1-alpha-2_NDS1.jar.
 Return code is: 401, ReasonPhrase:Unauthorized. -> [Help 1]


What I find strange is the reason for the failure is it didn't have an 
authorization challenge - yet the response code was 401 (un-authorised).

Anyone any ideas / workarounds?

Regards,

/James




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: pom formatter?

[Nord, James]

Thanks Stephen,

It appears to use spaces for the indentation of the moved block start tag - 
whereas the rest of the block (and the close) are left with tabs.
But otherwise just the ticket :-)

/James 


> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: 13 July 2012 14:56
> To: Maven Users List
> Subject: Re: pom formatter?
> 
> tidy-maven-plugin @ mojo (only a snapshot release) will apply the canonical
> pom ordering but does not handle indenting (in fact it tries to keep all the
> indenting the same
> 
> On 13 July 2012 14:49, Nord, James  wrote:
> 
> > Hi all,
> >
> > I'm wondering if anyone knows of a command line formatter for pom files?
> >
> > Not just converting tabs/spaces and line lengths but sorting out the
> > ordering of elements (model comes before parent which comes before
> > dependencies etc) (whilst also at the same time maintaining comments!).
> >
> > Does anyone know if such a beast exists?
> >
> > /James
> >
> >
> > 
> >
> >
> >
> >
> 
> **
> >  This message is confidential and intended only for
> > the addressee. If you have received this message in error, please
> > immediately notify the postmas...@nds.com and delete it from your
> > system as well as any copies.
> > The content of e-mails as well as traffic data may be monitored by NDS
> > for employment and security purposes. To protect the environment
> > please do not print this e-mail unless necessary.
> >
> > NDS Limited. Registered Office: One London Road, Staines, Middlesex,
> > TW18 4EX, United Kingdom. A company registered in England and Wales.
> > Registered no. 3080780. VAT no. GB 603 8808 40-00
> >
> >
> 
> **
> > 
> >

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

pom formatter?

[Nord, James]

Hi all,

I'm wondering if anyone knows of a command line formatter for pom files?

Not just converting tabs/spaces and line lengths but sorting out the ordering 
of elements (model comes before parent which comes before dependencies etc) 
(whilst also at the same time maintaining comments!).

Does anyone know if such a beast exists?

/James





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: [ANN] JAXB-2 Maven Plugin 1.4 Released

[Nord, James]

When I looked about 7 months ago the jvnet plugin supported episodes whereas 
the codehaus one did not.

/James

> -Original Message-
> From: Kathryn Huxtable [mailto:kath...@kathrynhuxtable.org]
> Sent: 26 June 2012 21:42
> To: Maven Users List
> Subject: Re: [ANN] JAXB-2 Maven Plugin 1.4 Released
>
> In general, how does this compare to the jvnet jaxb plugin? Why would I use
> one over the other?
>
> I do a certain amount of JAXB, and I'm curious.
>
> -K
>
> On Jun 26, 2012, at 3:20 PM, Anders Hammar wrote:
>
> > Hi,
> >
> > The Mojo team is pleased to announce the release of the JAXB-2 Maven
> > Plugin version 1.4.
> >
> > http://mojo.codehaus.org/jaxb2-maven-plugin/
> >
> > To get this update, simply specify the version in your project's
> > plugin configuration:
> >
> > 
> >  org.codehaus.mojo
> >  jaxb2-maven-plugin
> >  1.4
> > 
> >
> > Release Notes
> >
> > ** Bug
> >* [MJAXB-49] - Change the name of the plugin
> >
> > ** Improvement
> >* [MJAXB-30] - Patch to add support for Ant-style wildcards to 
> > schemaFiles
> >* [MJAXB-37] - Getters not being generated for Boolean fields
> >* [MJAXB-39] - Document use of schemagen target
> >* [MJAXB-48] - Make it possible to enable verbose from command line
> >* [MJAXB-53] - add an "encoding" parameter and use
> > ${project.build.sourceEncoding} as default value
> >* [MJAXB-59] - SchemaGen should skip non-existent source directories
> >* [MJAXB-60] - Improve m-compiler-p version lock-down in usage
> > pages
> >
> > ** New Feature
> >* [MJAXB-55] - Provide means to set the file name of generated XML
> > schema
> >
> > ** Task
> >* [MJAXB-50] - Document an example about having two (or more)
> > bindings with different config
> >
> >
> > Enjoy,
> >
> > The Mojo team.
> >
> > /Anders
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: sync to central and patched 3rd party artifacts

[Nord, James]

> > I was wondering how things are supposed to work when you have a sync
> > to central but you relly on a patched version of a 3rd party artifact.
> >
> > For example lets assume my library X depends on apache common io, and
> > the current version has a bug that has been sitting around with a path
> > for a while and not making it into any release.
>
> I would do everything that I could to get this patch applied by the dev team 
> and
> have another release produced by them with this fix included. Can you tell us
> the specific JIRA number which you are referencing?

Commons-io was just an example - I could just have easily said foobarwhizzylib.

Turns out the OSS product I was referening to actually deploys the patched libs 
under its own GAV which I missed when looking at it - so this isn’t actually an 
issue to me anymore.

> Otherwise you would follow these directions:
> https://docs.sonatype.org/display/Repository/Uploading+3rd-
> party+Artifacts+to+The+Central+Repository


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

sync to central and patched 3rd party artifacts

[Nord, James]

Hi all,

I was wondering how things are supposed to work when you have a sync to central 
but you relly on a patched version of a 3rd party artifact.

For example lets assume my library X depends on apache common io, and the 
current version has a bug that has been sitting around with a path for a while 
and not making it into any release.
So according to the documents normally we would download and build a patched 
verison of commons:commons-io and deploy it to our repo as 
common:commons-io:1.2.3-4_JIRA1234

Using the same Group and artifact is recommended to avoid bringin in duplicate 
classes is someone who consumes our lib also uses commons-io.

Anyway this is all good - but what happens if we want our artifact X synced to 
central - we must have all dependencies available on central but we have no 
sync control on commons/commons-io.

What would normally happen here?

/James



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: compiler errors hidden when building Maven project on Jenkins

[Nord, James]

Moving to Jenkins-dev (if anyone wants to follow there)

> > I say no - except if you use any plugin that behind the scenes changes the
> configuration of the mojos you run.
> > I'm open for someone to convince me I'm wrong though.
> >
> > I haven't taken an in depth look but IIRC a Jenkins plugin can't subvert the
> maven build by changing mojo parameters on the fly anymore if you use
> Maven 3.x (in a Maven2 job).
>
> does your build fail if the tests fail?

Depends on what type of build I'm running  (code review, commit or full).

> if the answer is no, and you haven't put -Dmaven.test.failure.ignore=true on 
> the
> CLI then you are recalling incorrectly :-P

But - is this any different to someone hiding away MAVEN_OPTS somewhere in the 
global or slave configuration that a non admin user can't see?
All be it this info should really be echoed in the build log (regardless of 
freestyle or maven2 job type) but that is a different discussion.

The bit I was referring to was from MojoInfo.java:

/**
 * Mojo object that carries out the actual execution.
 *
 * @deprecated as of 1.427
 *  Maven3 can no longer provide this information, so plugins cannot 
rely on this value being present.
 *  For the time being we are setting a dummy value to avoid NPE. Use 
{@link #configuration} to access
 *  configuration values, but otherwise the ability to inject values is 
lost and there's no viable
 *  alternative.
 */
public final Mojo mojo;

Are you saying that all the manipulation of the configuration can still be done 
on the fly per mojo per module - and it is not done up-front by a system 
property or some other mechanism)?

/James



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: compiler errors hidden when building Maven project on Jenkins

[Nord, James]

Some people (like Stephen) will say yes.

I say no - except if you use any plugin that behind the scenes changes the 
configuration of the mojos you run.
I'm open for someone to convince me I'm wrong though.

I haven't taken an in depth look but IIRC a Jenkins plugin can't subvert the 
maven build by changing mojo parameters on the fly anymore if you use Maven 3.x 
(in a Maven2 job).

/James

-Original Message-
From: Drury, Tim [mailto:t.dr...@sap.com]
Sent: 14 February 2012 16:14
To: Maven Users List
Subject: RE: compiler errors hidden when building Maven project on Jenkins

>And the OP is probably using the "evil" Maven project type and not a
>freestyle project with a maven build step

I am.  Is this bad?

-tim

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

Skip surefire but run failsafe?

[Nord, James]

Hi all,

Is there a way to run failsafe base integration tests but not surefire based 
unit tests? (using the lifecycle as I still need to generate a lot of sources 
etc...)

I tried mvn -DskipTests=true -DskipITs=false verify but also this is skipping 
both surefire and failsafe

[INFO] --- maven-surefire-plugin:2.8.1:test (default-test) @ myproj ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ myproj ---
[INFO]
[INFO] --- maven-failsafe-plugin:2.7.2:integration-test (integration-test) @ 
myproj ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-source-plugin:2.1:jar-no-fork (attach-sources) @ myproj ---
[INFO]
[INFO] --- maven-source-plugin:2.1:test-jar-no-fork (attach-sources) @ myproj 
---
[INFO]
[INFO] --- maven-failsafe-plugin:2.7.2:verify (verify) @ myproj ---
[INFO] Tests are skipped.
[INFO] 
[INFO] BUILD SUCCESS

Is there a way to accomplish this?

/James



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Maven is using SNAPSHOT versions of plugins

[Nord, James]

Most likely because you are using a repository manager (nexus / artifactory?) 
and a settings.xml that is incorrect configured.

http://maven.40175.n5.nabble.com/Plugins-snapshot-resolution-td4833804.html

and http://maven.40175.n5.nabble.com/settings-xml-td131025.html for a solution 
that "works for me(tm)"

/james

-Original Message-
From: jeffma...@gmail.com [mailto:jeffma...@gmail.com] On Behalf Of Jeff MAURY
Sent: 04 January 2012 16:02
To: Maven Users List
Subject: Re: Maven is using SNAPSHOT versions of plugins

SNAPSHOT are not available in central repository.

Jeff MAURY

On Wed, Jan 4, 2012 at 2:17 PM, Abid Hussain  wrote:

> Hi all,
>
> trying to create a project using the archetype-plugin fails because
> maven tries to use a SNAPSHOT version of the plugin:
> [INFO] Unable to find resource
> 'org.apache.maven.plugins:maven-archetype-plugin:maven-plugin:2.3-SNAPSHOT'
> in repository central (http://central) [INFO]
> --
> --
> [ERROR] BUILD FAILURE
> [INFO]
> --
> -- [INFO] A required plugin was not found: Plugin could not be found -
> check that the goal name is correct: Unable to download the artifact
> from any repository
>
> Same happens when trying to perform the maven-eclipse-plugin. So my
> question is: why does maven try to use SNAPSHOT versions which do not
> exist? Can the cause of the problem be in my local configuration?
>
> Regards,
>
> Abid
> --
> NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
> Jetzt informieren: http://www.gmx.net/de/go/freephone
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


--
"Legacy code" often differs from its suggested alternative by actually working 
and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: Properties in settings.xml does not work for system scoped dependencies

[Nord, James]

Not that I am needing to do this but in order to further my understanding...

If you create an Uber JAR - then you can end up in classpath hell - as the 
dependencies aren't correct (it could include common-io 1.2 and you need 
commons-io 1.3 which is declared transitively)  This then means that even 
though you don't depend on commons-io you need to start adding all transitive 
dependencies to your pom just incase the app server ships with a different one 
and the uber jar takes precedence over the transitive dependency.  The J2EE 
container should allow you to override some bits of the provide jars should 
they not?

/James

-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: 15 November 2011 08:26
To: Maven Users List
Subject: Re: Properties in settings.xml does not work for system scoped 
dependencies

the correct scope for those deps should be provided imho.

the problem you have is getting the deps you need, system scope is just a 
workaround.

ideally you would create an uberjar from the geologic jar and just install that 
into your repo manager.

the focus should be on taking a jar and making an uberjar from its manifest 
classpath... should be easy, then install that uberjar in your repo. forget 
about identifying which of the 480 odd jars has your dep, when you depend on 
geologic specific classes, that's what you need.

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense words 
and other nonsense are a direct result of using swype to type on the screen On 
15 Nov 2011 03:19, "Stephen Coy"  wrote:

> Hi there,
>
> I've been a maven user since the early 1.0 days and have contributed
> patches at various times for the ejb-plugin, ear-plugin and others.
>
> I've also had the unfortunate experience of having to use WebLogic 10+
> to create useable maven poms for our projects. In fact, when I read
> the OP I knew he was talking about Weblogic even though he did not mention it.
>
> The *only* way I've been able to do this successfully was with a
> system scoped dependency on the weblogic.jar.
>
> This is because weblogic contains a maze of relative manifest class
> paths that are truly mind boggling.
>
> The very first class path entry in weblogic.jar looks like:
>
> ../../../modules/features/weblogic.server.modules_10.3.5.0.jar
> (plus a dozen or more others)
>
> That modules directory contains 465 (very OSGI looking) jars and sub
> directories. Do you really think it's practical to install all of
> these into a repository manager? How would you generate the
> dependencies for each pom?
>
> This would not be an issue for any "plain old JEE" application.
> However, if you have any need at all for weblogic specific APIs then a
> system scoped dependency is the only practical way. Even when you do
> figure out which one of those ~500 jars contains your API, you then
> need to read it's manifest and pick out its dependencies, and then the 
> dependencies' dependencies, etc.
>
> If someone has a simple solution to this then I'd like to hear it too.
> Otherwise, *please* restore the system scope functionality.
>
>
> Cheers,
>
> Steve C
>
>
> On 14/11/2011, at 2:55 AM, Benson Margulies wrote:
>
> > No possible licensing restriction can prevent you from having your
> > own shared repository with nexus or archiva or artifactory and
> > pushing whatever you want to it.
> >
> > For that matter, it's not too hard to write a script that calls
> > install:install-file on each of a pile of jar files. You can't do
> > this in the reactor and then use the results (AFAIK), but you can
> > run this and then run the build.
> >
> > In other words, anything you can do with system scope you can do
> > with less headaches with a repo manager or instal:install-file.
> >
> >
> > On Sat, Nov 12, 2011 at 8:20 AM, Bengt Rodehav 
> wrote:
> >> Last time I went through this I never came all the way to a
> >> complete
> list
> >> but I do remember there were lots of jars missing. I guess I'll
> >> have to reiterate this again since system scope doesn't seem to be
> >> supported anymore.
> >>
> >> /Bengt
> >>
> >> 2011/11/12 Wayne Fay 
> >>
> >>> What else do you need? Why not full client + some reasonable
> >>> (small) handful of other dependencies?
> >>>
> >>> Wayne
> >>>
> >>> On Fri, Nov 11, 2011 at 5:00 PM, Bengt Rodehav 
> wrote:
>  It works but the full client is not enough for us to be able to
>  build
> our
>  application.
> 
>  Den 11 nov 2011 23:11 skrev "Ryan Connolly" :
> >
> > Does this no longer work?
> > http://docs.oracle.com/cd/E12840_01/wls/docs103/client/t3.html
> > On Nov 11, 2011 3:38 PM, "Bengt Rodehav"  wrote:
> >
> >> Stephen and Wayne,
> >>
> >> I agree that using system scope is undesirable. However, there
> >> is a
>  reason
> >> why maven has had this  support - it is needed in real life. In
> >> my
>  case, I
> >> use Weblogic. When first trying to m

RE: Error during release:perform with multi-module git project on Windows

[Nord, James]

Cygwin, cmd and git can get in each others way and confuse things.
do you have the ability to try from a cmd.exe console and with the native git 
port?

/James

-Original Message-
From: codingplayer [mailto:roman.ce...@smartengine.at]
Sent: 20 October 2011 10:25
To: users@maven.apache.org
Subject: Re: Error during release:perform with multi-module git project on 
Windows

Hi,

we currently experience the same problem.

running mvn release:prepare (on a Windows 7 machine from a cygwin console) in a 
module-project fails with the following error:

[INFO] Executing: cmd.exe /X /C "git add -- pom.xml 
C:\DATA\Workspace\sandbox\sandbox-module1\pom.xml
C:\DATA\Workspace\sandbox\sandbox-module2\pom.xml
C:\DATA\Workspace\sandbox\sandbox-module2\sandbox-module2-submodule1\pom.xml"
[INFO] Working directory: c:\DATA\Workspace\sandbox [INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Smart Engine - Sandbox  FAILURE [0.547s] 
[INFO] Smart Engine - Sandbox - First Module . SKIPPED [INFO] Smart 
Engine - Sandbox - Second Module  SKIPPED [INFO] Smart Engine - 
Sandbox - Second Module's First Submodule  SKIPPED [INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 1.221s
[INFO] Finished at: Thu Oct 20 11:00:00 CEST 2011 [INFO] Final Memory: 22M/981M 
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.2.1:rollback (default-cli) on 
project sandbox: Unable to commit files [ERROR] Provider message:
[ERROR] The git-add command failed.
[ERROR] Command output:
[ERROR] fatal: 'C:\DATA\Workspace\sandbox\sandbox-module1\pom.xml' is outside 
repository


We are using the latest release version of the maven-release-plugin:


2.2.1



org.apache.maven.plugins
maven-release-plugin
${release.plugin.version}


And yes, the parent project is a git repository:

myusername@mymachine /c/DATA/Workspace/sandbox (release/1.0)
$ git status
# On branch release/1.0
nothing to commit (working directory clean)

Are there any workarounds or any solutions yet?

br
R.C.

--
View this message in context: 
http://maven.40175.n5.nabble.com/Error-during-release-perform-with-multi-module-git-project-on-Windows-tp4610985p4920884.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

compressing site documentation?

[Nord, James]

Hi all,

The Maven sites can get quite large (clover, javadoc, source xref) and when 
there are lots of projects and versions you can eat 100's of GB quite easily.  
They also compress exceptionally well.

Does anyone know of an existing maven plugin that can compress (gzip) the html 
(and css?) files so the server can server them compressed to clients (or 
decompress them on the fly for those that don't support gzip encoding)?

Regards,

/James



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Multi-module release:prepare creates a tag that includes the tags folder

[Nord, James]

Well you scm setting seems to be wrong.

For your parent module it needs to be

scm:svn:svn://localhost/project/trunk/parent/

scm:svn:svn://localhost/project/trunk/parent
scm:svn:svn://localhost/project/trunk/parent


Same for all other modules.


-Original Message-
From: Caristi, Joe [mailto:jcari...@whisolutions.com]
Sent: 05 May 2011 21:16
To: users@maven.apache.org
Subject: Multi-module release:prepare creates a tag that includes the tags 
folder

I am attempting to use the Maven Release plugin with Maven 3.0.3 to release a 
flat multi-module structure in Subversion.  I have the release:prepare goal 
working well except for one thing.  The tagged release includes the tags 
folder, which is a sibling of the trunk.  Does anyone know how to prevent this 
from happening?  I expected only the trunk folder to be in the tag.

Here are the details:

commitByProject=true (set on command line) autoVersionSubmodules= true (set in 
release profile in parent-module pom)

SCM settings:


scm:svn:svn://localhost/project/trunk

scm:svn:svn://localhost/project/trunk
scm:svn:svn://localhost/project/trunk


My Subversion folder structure looks like this:


project /

  +- tags /

  +- trunk /

 +- parent /

 +- child1 /

 +- child2 /



After running release:prepare on the parent-module for version 1.0.1, which 
sets all my versions properly and creates a tag, I end up with this:



project /

  +- tags /

+- parent-1.0.1 /

+- tags /

+- trunk /

  +- parent /

  +- child1 /

  +- child2 /

  +- trunk /

 +- parent /

 +- child1 /

 +- child2 /

The first time I tried this, the nested tags folder was empty.  On subsequent 
runs, it contains all the tags from the previous run:


project /

  +- tags /

 +- parent-1.0.1 /

+- tags /

+- trunk /

  +- parent /

  +- child1 /

  +- child2 /

 +- parent-1.0.2 /

+- tags /

   +- parent-1.0.1 /

  +- tags /

  +- trunk /

+- parent /

+- child1 /

+- child2 /

+- trunk /

  +- parent /

  +- child1 /

  +- child2 /

  +- trunk /

 +- parent /

 +- child1 /

 +- child2 /






STATEMENT OF CONFIDENTIALITY:



The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain confidential or privileged information. If you are not the intended 
recipient, please notify WHI Solutions immediately at g...@whisolutions.com, 
and destroy all copies of this message and any attachments.


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: central repo?

[Nord, James]

Hi Brian,

"we incorporate the feedback we received and ensure the index used to render 
the browse is completely in lockstep with the contents."

Interesting...  Are all the mirrors updated atomically with repo1 (I didn't 
think they where) so the engineering effort in this must be huge :-)

Just don't want it forgotten that just as it is in repo1.m.o it may not be in 
uk.m.o  (and if it is in the process of being synced could be only be partially 
there?)

Thanks for the quick workaround.

/James

-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: 05 May 2011 17:53
To: Maven Users List
Subject: Re: central repo?

Than you, i'll let the team know.
http://repo2.maven.org/maven2/org/
Also, we've adjusted how the redirects work and included a static page so 
people don't feel like the repo was hijacked:

Deeper links to artifact folders will show the older index view for now until 
we incorporate the feedback we received and ensure the index used to render the 
browse is completely in lockstep with the contents.

On Thu, May 5, 2011 at 12:17 PM, Jim McCaskey  
wrote:
> So, I'm not sure anyone here will care about this.  But Maven Central does 
> not work with IE9.
>
> You get an error like this:
>
> When a website causes a failure or crash, Internet Explorer attempts to 
> restore the site. It stops after two tries to avoid an endless loop.
>
> And the URL switches to this:
>
> res://ieframe.dll/acr_error.htm#maven.org,http://search.maven.org/#bro
> wse
>
> I had a friend try his system with IE8 and it worked fine.  Needless to say 
> Chrome and FF work just fine.
>
> -Jim
>
> -Original Message-
> From: Brian Fox [mailto:bri...@infinity.nu]
> Sent: Thursday, May 05, 2011 8:50 AM
> To: Maven Users List
> Subject: Re: central repo?
>
> On Thu, May 5, 2011 at 7:09 AM, Anders Hammar  wrote:
>> Regarding the "m2e indexes", at what time are they updated?
>
> 3:22 CST daily.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: central repo?

[Nord, James]

Hi Brian,

I understand the reasons and I'm all for it - but there needs to be a way to 
easily diagnose issues for people that look after maven proxies (such as a 
corporate nexus instance) when there are issues with artifacts.  The old http 
directory listings enabled just that.

Apart from the above I actually liked search.m.o and was impressed by its speed 
(seemed quicker than nexus when searching!).

OT: when you download an artifact from search.m.o does it give you your local 
mirror (uk in my case) or does it travel across the pond and download from 
repo1.m.o?

Regards,

/james

-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu] 
Sent: 05 May 2011 12:06
To: Maven Users List
Subject: Re: central repo?

This was an attempt to block the constant scrapers that are attempting to crawl 
the entire repository for no good reason, and the bandwidth isn't free.

The index used to serve the search is not the same index used by M2e.
Fwiw, the m2e indexes are updated daily now, but I need to see why this index 
was out of date.

Regardless, we'll go back to the drawing board and see how to make this less of 
a hurdle, while still interrupting the scrapers.

On Wed, May 4, 2011 at 6:27 PM, Nord, James  wrote:
> That doesn't browse the repo it browses what it thinks is the repo (or 
> the index...)
>
> e.g. there is no org.eclipse.tycho but there is
>
> Also which repo does it think that is - the UK mirror whuch may or may not be 
> updated with the latest deployment??!?
>
> http://repo1.maven.org/maven2/org/eclipse/tycho/tycho-maven-plugin/mav
> en-metadata.xml (is ok)
>
> there is no org/eclipse/tycho according to 
> http://search.maven.org/#browse%7C1428323731
>
> /James - ie let me see the real think not the index that is wrong most 
> of the time
>
>
> -Original Message-
> From: Arnaud Héritier [mailto:aherit...@gmail.com]
> Sent: 04 May 2011 23:24
> To: Maven Users List
> Subject: Re: central repo?
>
> Hi,
>
> You can continue to browse the repository from here :
> http://search.maven.org/#browse%7C47
>
> Is it what you searched ?
>
> Arnaud
>
> On Thu, May 5, 2011 at 12:09 AM, Nord, James  wrote:
>
>> Hi all,
>>
>> What happened recently to the central repos and their mirrors (uk).
>>
>> When I try to browse I now get redirected to search.maven.org which 
>> is not a good thing when trying to work out why something isn't 
>> working as expected when proxied via a repo manager.
>>
>> Also I guess these searches run of the index - but as far as I have 
>> always been led to believe the indexes are correct on Sunday only, 
>> and don't help when the metadata is incorrect.
>>
>> How can I get back to the old bog standard directory listings 
>> produced by the web server?
>>
>> /james
>>
>>
>>
>> 
>>
>>
>> *
>> *
>>  This message is confidential and intended only for 
>> the addressee. If you have received this message in error, please 
>> immediately notify the postmas...@nds.com and delete it from your 
>> system as well as any copies.
>> The content of e-mails as well as traffic data may be monitored by 
>> NDS for employment and security purposes. To protect the environment 
>> please do not print this e-mail unless necessary.
>>
>> NDS Limited. Registered Office: One London Road, Staines, Middlesex,
>> TW18 4EX, United Kingdom. A company registered in England and Wales.
>> Registered no. 3080780. VAT no. GB 603 8808 40-00
>>
>> *
>> *
>> 
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

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


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

RE: central repo?

[Nord, James]

That doesn't browse the repo it browses what it thinks is the repo (or the 
index...)

e.g. there is no org.eclipse.tycho but there is

Also which repo does it think that is - the UK mirror whuch may or may not be 
updated with the latest deployment??!?

http://repo1.maven.org/maven2/org/eclipse/tycho/tycho-maven-plugin/maven-metadata.xml
 (is ok)

there is no org/eclipse/tycho according to 
http://search.maven.org/#browse%7C1428323731

/James - ie let me see the real think not the index that is wrong most of the 
time


-Original Message-
From: Arnaud Héritier [mailto:aherit...@gmail.com] 
Sent: 04 May 2011 23:24
To: Maven Users List
Subject: Re: central repo?

Hi,

You can continue to browse the repository from here :
http://search.maven.org/#browse%7C47

Is it what you searched ?

Arnaud

On Thu, May 5, 2011 at 12:09 AM, Nord, James  wrote:

> Hi all,
>
> What happened recently to the central repos and their mirrors (uk).
>
> When I try to browse I now get redirected to search.maven.org which is 
> not a good thing when trying to work out why something isn't working 
> as expected when proxied via a repo manager.
>
> Also I guess these searches run of the index - but as far as I have 
> always been led to believe the indexes are correct on Sunday only, and 
> don't help when the metadata is incorrect.
>
> How can I get back to the old bog standard directory listings produced 
> by the web server?
>
> /james
>
>
>
> 
>
>
> **
>  This message is confidential and intended only for 
> the addressee. If you have received this message in error, please 
> immediately notify the postmas...@nds.com and delete it from your 
> system as well as any copies.
> The content of e-mails as well as traffic data may be monitored by NDS 
> for employment and security purposes. To protect the environment 
> please do not print this e-mail unless necessary.
>
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, 
> TW18 4EX, United Kingdom. A company registered in England and Wales. 
> Registered no. 3080780. VAT no. GB 603 8808 40-00
>
> **
> 
>

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

central repo?

[Nord, James]

Hi all,

What happened recently to the central repos and their mirrors (uk).

When I try to browse I now get redirected to search.maven.org which is not a 
good thing when trying to work out why something isn't working as expected when 
proxied via a repo manager.

Also I guess these searches run of the index - but as far as I have always been 
led to believe the indexes are correct on Sunday only, and don't help when the 
metadata is incorrect.

How can I get back to the old bog standard directory listings produced by the 
web server?

/james





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Is maven3 repository safe for concurrent access

[Nord, James]

The benefits are things like if one ci job does 
mvn install and fails for some modules (say unit test failures) - you will end 
up with these broken modules being in the repository for other jobs to consume.

You can completely wipe it for each full build (if you distinguish between 
commit/smoke and full build) to make sure it is always reproducible (without 
wiping out artifacts for some other job that is currently building and then 
getting arbitrary failures.)

BTW - it sounds like you aren't using a maven proxy - I would highly recommend 
it in a corporate environment, artifactory and nexus are the two big players in 
this field, as it will shield you from network glitches, and ease consumption 
of your builds in other builds, and using libs that aren't in the maven 
ecosystem.

/james


-Original Message-
From: Sony Antony [mailto:sony.ant...@gmail.com] 
Sent: 15 April 2011 21:07
To: Maven Users List
Subject: Re: Is maven3 repository safe for concurrent access

Thanks a real lot James :
I was not aware of maven.repo.local ( although I was aware of teh setting.xml 
optio to specify the local repository ). We have decided to use this.

1. "which gives other benefits other than just its safe"
Do you mind explaining some of the other benefits we might reap with seperate 
local repo.

2. While looking up the maven.repo.local, you mentioned, I came across 
maven.repo.remote, which takes multiple comma seperated URLs. I was wondering 
if I could use a file:/// style URL on this. So that we can have a single 
read-only secondary local repository, hosting all teh third party software and 
plugins ( without having to host them in a internal corporate web server )

( different maven.repo.local for each instances will require teh same 
thirdparty software/plugins to be duplicated in multiple places )


--sony




On Fri, Apr 15, 2011 at 3:44 PM, Nord, James  wrote:

> Hi Sony,
>
> You can just configure a separate local repo for each CI job (which 
> gives other benefits other than just its safe).
>
> Hudson/Jenkins can do this for you (use private repository option)
>
> Otherwise use "mvn  -Dmaven.repo.local=/path/to/job/specific/repo
> "
> Or set it in your settings file (which you can then specify also per 
> job with -s)
>
> /james
>
>
> -Original Message-
> From: Sony Antony [mailto:sony.ant...@gmail.com]
> Sent: 15 April 2011 20:31
> To: Maven Users List
> Subject: Re: Is maven3 repository safe for concurrent access
>
> You are correct. My interest is in knowing if I can use maven under a 
> CI/hudson  environment ( with multiple seperate instances of maven 
> running ).
> If there is a patch for this, can somebody please post its reference 
> here
>
> --sony
>
> On Fri, Apr 15, 2011 at 3:23 PM, Mirko Friedenhagen < 
> mfriedenha...@gmail.com
> > wrote:
>
> > On Fri, Apr 15, 2011 at 19:39, Kristian Rosenvold 
> >  wrote:
> > >
> > > fr., 15.04.2011 kl. 11.54 -0400, skrev Sony Antony:
> > >> Thank you Jason :
> > >> If 3.x local repository is not safe for concurrent access, how 
> > >> does
> > maven3
> > >>  implement parallel builds ( -T switch ) ( maybe they decide on 
> > >> teh parallelism by making sure that there is no concurrent 
> > >> read/write access on teh repository *for the same* artifacts
> > ? )
> > >>
> > >
> > > The first half you got right, there is no concurrent writes of the 
> > > each individual artifact "by design".
> > >
> > > When it comes to downloading from remote repositories it's all 
> > > handled by a common (singleton) service anyway.
> >
> > This is only correct for one single instance of maven running, where 
> > multiple threads are downloading artifacts, isn't it? I guess the OP 
> > wanted to know wether it is safe to use Maven3 in a CI, where 
> > multiple processes download dependencies. To my understanding it is 
> > not safe, there was a patch for Maven2, if I remember right.
> >
> > Regards
> > Mirko
> > --
> > http://illegalstateexception.blogspot.com/
> > https://github.com/mfriedenhagen/
> > https://bitbucket.org/mfriedenhagen/
> >
> > 
> > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
>
>
> **
>  This message is confidential and intended only for 
> the addressee. If you have received this message in error, please 
> immediately notify t

RE: Is maven3 repository safe for concurrent access

[Nord, James]

Hi Sony,

You can just configure a separate local repo for each CI job (which gives other 
benefits other than just its safe).

Hudson/Jenkins can do this for you (use private repository option)

Otherwise use "mvn  -Dmaven.repo.local=/path/to/job/specific/repo 
"
Or set it in your settings file (which you can then specify also per job with 
-s)

/james


-Original Message-
From: Sony Antony [mailto:sony.ant...@gmail.com]
Sent: 15 April 2011 20:31
To: Maven Users List
Subject: Re: Is maven3 repository safe for concurrent access

You are correct. My interest is in knowing if I can use maven under a CI/hudson 
 environment ( with multiple seperate instances of maven running ).
If there is a patch for this, can somebody please post its reference here

--sony

On Fri, Apr 15, 2011 at 3:23 PM, Mirko Friedenhagen  wrote:

> On Fri, Apr 15, 2011 at 19:39, Kristian Rosenvold
>  wrote:
> >
> > fr., 15.04.2011 kl. 11.54 -0400, skrev Sony Antony:
> >> Thank you Jason :
> >> If 3.x local repository is not safe for concurrent access, how does
> maven3
> >>  implement parallel builds ( -T switch ) ( maybe they decide on teh
> >> parallelism by making sure that there is no concurrent read/write
> >> access on teh repository *for the same* artifacts
> ? )
> >>
> >
> > The first half you got right, there is no concurrent writes of the
> > each individual artifact "by design".
> >
> > When it comes to downloading from remote repositories it's all
> > handled by a common (singleton) service anyway.
>
> This is only correct for one single instance of maven running, where
> multiple threads are downloading artifacts, isn't it? I guess the OP
> wanted to know wether it is safe to use Maven3 in a CI, where multiple
> processes download dependencies. To my understanding it is not safe,
> there was a patch for Maven2, if I remember right.
>
> Regards
> Mirko
> --
> http://illegalstateexception.blogspot.com/
> https://github.com/mfriedenhagen/
> https://bitbucket.org/mfriedenhagen/
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: Script/plugin to play sound when maven build finishes?

[Nord, James]

You can run the CI server on your local sources on your local desktop - no need 
to install it on any server.

Alternativley
mvn foo:bar & playSound

you just need to find a command line tool that can play a sound.

/James
-Original Message-
From: John Lussmyer [mailto:john.lussm...@amdocs.com]
Sent: 18 March 2011 16:48
To: Maven Users List
Subject: RE: Script/plugin to play sound when maven build finishes?

??? How would a build running on a Server play a sound on my machine when I do 
a build on my machine?
I need this for builds I run on my machine BEFORE I check them in.

-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Friday, March 18, 2011 9:38 AM
To: Maven Users List
Subject: Re: Script/plugin to play sound when maven build finishes?

Sounds like something I would do using my continuous integration server. Look 
into Hudson/Jenkins and there's probably a plugin to do this kind of thing for 
you.

Wayne

On Fri, Mar 18, 2011 at 10:22 AM, John Lussmyer  
wrote:
> I'm using Maven on a Fedora system, and it would be REALLY helpful if Maven 
> would play a sound when a build finished.
> Anyone have any easy way to do that?
> (and I am NOT a shell script expert, so please don't say "just write a
> script".  If you must say that, please provide the script.)
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: subversion vs maven

[Nord, James]

There is an option "Incremental build - only build changed modules" under the 
advanced section of the Build options (for an M2 build).

If checked, Hudson will only build any modules with changes from SCM and any 
modules which depend on those changed modules, using Maven's "-amd -pl 
group1:artifact1,group1:artifact2" command-line options. If the SCM reports no 
changes to any modules, however, all modules will be built. See 
http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode for more 
information on the Maven behavior this utilizes.

This functionality requires Maven 2.1 or later, and will not have any impact if 
"Build modules in parallel" is selected.

Any follow-up on this should be directed at the Jenkins or Hudson users lists.

/James

-Original Message-
From: Zilvinas Vilutis [mailto:cika...@gmail.com]
Sent: 16 February 2011 17:18
To: Leon Rosenberg
Cc: Maven Users List
Subject: Re: subversion vs maven

Yes,

However it does a "full build" which takes ~30-40 minutes. But I want to build 
only specific projects and their dependents.

Regards

Žilvinas Vilutis

Mobile:   (+370) 652 38353
E-mail:   cika...@gmail.com



On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg  
wrote:
> How about hudson?
>
> Hudson can watch for svn changes and trigger builds on commit.
>
> regards
> Leon
>
> On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis  wrote:
>> Hello Maven Users!
>>
>> Probably this question was already asked, so if there is an answer
>> which I could not find - please point me to the right place.
>>
>>
>> I'm working on an enterprise project where maven integration plays a huge 
>> role.
>>
>> However the project is big as a lot of teams are working on it and it
>> takes quite some time to build it ( 30-40 minutes ), which I need to
>> do every morning after an svn update.
>>
>>
>> So I was thinking - is there any way to configure maven to build only
>> the projects which were updated by SVN ( e.g. in the script time )?
>>
>>
>> Most likely there is no direct answer...however, I think that I could
>> find a way to gather the project names which were updated in the
>> shell script - then I could pass the list of project names to maven command.
>> Is there any way to make sure that those and dependent projects would
>> be built in the right order?
>>
>>
>> The project structure is:
>>
>> parent
>> -- subsystem1
>>  -- s1-project1
>>  -- s1-project2
>> -- subsystem2
>>  -- s2-project1
>>  -- s2-project2
>>  -- s2-project3
>> -- subsystem3
>>  -- s3-project1
>>
>>
>> Thank you for any ideas!
>>
>>
>> Žilvinas Vilutis
>>
>> Mobile:   (+370) 652 38353
>> E-mail:   cika...@gmail.com
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Skipping rpm build under windows

[Nord, James]

-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: 17 January 2011 16:49
To: Maven Users List
Subject: Re: Skipping rpm build under windows

> You can use a profile to build your rpm project.

This would normally be my response too... but I personally dislike profiles for 
things if there is another way to handle it. Profiles can make builds more 
complicated than absolutely necessary.

Surely the rpmbuild plugin could be adjusted to check the OS, or check for the 
existence of the "rpmbuild" executable or something, and then ignore with a 
warning (or fail, configurable in the plugin config) if it wasn't found, or 
something...? This just seems like a common use case and maybe the rpmbuild 
plugin devs should find a little bit smarter way to handle it.

[JN] But then you run the release on a unix box that hasn't had RPMBuild 
installed and it completes (no one ever checks the warnings right yet there is 
no rpm!)
But it's ok as you can then have a profile to enable the 
doNotFailIfRPMBuildIsNotFound - but then you don't like profiles and you are 
back where you started...

IIRC the rpm plugin works on windows if you have Cygwin installed and the 
rpmbuild package for the anti-profile people out there.

/James


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Missing goal eclipse:m2eclipse in version 2.8 of the Maven Eclipse plugin

[Nord, James]

You can't (in 2.8) - you can specify the old version of the plugin with the 
m2eclipse goal on the command line.

Or (preffered)
just import the projects in eclipse as maven projects, and let m2eclipse create 
your project files with the correct natures.

/James

-Original Message-
From: Stefan Eder [mailto:stefan.e...@ebuconnect.de]
Sent: 16 December 2010 11:09
To: users@maven.apache.org
Subject: Missing goal eclipse:m2eclipse in version 2.8 of the Maven Eclipse 
plugin

  Hi,

since quite a while I am using Maven and Eclipse together with the Eclipse 
plugin for Maven and the Maven plugin for Eclipse. And it is just great.

But in the version 2.8 of the Eclipse plugin for Maven I am (hardly) missing 
the goal m2eclipse.

How can I tell the version 2.8 of the Eclipse plugin to create .classpath files 
that refer to MAVEN2_CLASSPATH_CONTAINER and to add Maven nature and build 
command to the .project files without touching the corresponding poms?

Thanks,
Stefan

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Nested Modules Not Working with 20101115-1102 Update

[Nord, James]

I can read minds and he is referring to m2eclipse.

I should point out that the mailing list for m2eclipse users can be found at 
https://dev.eclipse.org/mailman/listinfo/m2e-users

/James

-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: 24 November 2010 21:14
To: Maven Users List
Subject: Re: Nested Modules Not Working with 20101115-1102 Update

> I just recently updated to version 0.12.0.20101115-1102 and my project with
> nested modules no longer has any maven dependencies.  I was not able find a

Version 0.12.0.xyz of what exactly??

Wayne

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: maven-metadata containing SNAPSHOT versions when Nexus group references release proxy repo

[Nord, James]

A repo manager must be able to cope with the junk/good stuff that other people 
setup so long as it is valid it should not do anything that will break Maven.
This is especially true if the repo manager makes the assumption that you can 
only ever have a release only or a snapshot only repository as it will break 
Maven when it thinks it can get something but actually can't!

java.net and all those mixed repos are perfectly valid maven repos (even if 
they *should* really split releases from snapshots)

Do you think it is acceptable for a repo manager to break Maven?

/James

-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of 
Anders Hammar
Sent: 11 November 2010 11:56
To: Maven Users List
Cc: Jane Young; Bill Shannon
Subject: Re: maven-metadata containing SNAPSHOT versions when Nexus group 
references release proxy repo

I don't know. If it's a mixed repo at origin, why must a repo manager be
able to change that to a release only repo?
Sure, it could be nice, but I don't see why it must be able to. Complain to
the people that set up the repo instead.

/Anders
On Thu, Nov 11, 2010 at 12:25, Nord, James  wrote:

> Repo managers must be able to cope with this.  Where is the release only
> version of java.net?
>
> /James
>
> -Original Message-
> From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
> Behalf Of Anders Hammar
> Sent: 11 November 2010 11:10
> To: Jane Young; Maven Users List
> Cc: Bill Shannon
> Subject: Re: maven-metadata containing SNAPSHOT versions when Nexus group
> references release proxy repo
>
> I think that the main problem is that you're specying the repo as a release
> repo. It's a mixed repo as it contains snapshots.
>
> /Anders
>
> On Thu, Nov 11, 2010 at 11:29, Jane Young  wrote:
>
> >  If I create a proxy repo in Nexus with policy set as "release" and it's
> > referencing the group repo that contains SNAPSHOTs.  Should the proxy
> repo
> > contain SNAPSHOT artifacts?  No...  but the metadata contains the
> SNAPSHOT
> > versions.  Isn't this a discrepancy?
> >
> > Furthermore, if the pom file is referencing this proxy repo and has a
> > dependency on a maven plugin, maven will try to download the latest
> version
> > that is defined in metadata and the build is going to fail since the
> > SNAPSHOT artifact is not available.
> >
> > If this is not a bug, how do you work around it?
> >
> >
> >
> >
> > On 11/11/10 2:16 AM, Anders Hammar wrote:
> >
> > The first repos are group repos. The latter one is just a repo. You can
> > tell from the urls.
> >
> > If the group repo contains a snapshot proxy repo, it will contain
> snapshot
> > info in the metadata. It's not a bug.
> >
> > /Anders
> >
> > On Thu, Nov 11, 2010 at 11:12, Jane Young  wrote:
> >
> >> Hi Anders,
> >>
> >> The reason GlassFish Nexus group repository is  referencing
> >> http://repository.jboss.org/nexus/content/groups/public/  is because it
> >> contains specific glassfish  versions of Weld artifacts.
> >> See:
> >>
> >>
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/weld-osgi-bundle/
> >> vs
> >>
> >>
> http://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/weld/weld-osgi-bundle/
> >>
> >> Also, the repository is recommended by Pete Muir (Weld project lead).
> >>
> >> Is there another JBoss repository that does not contain SNAPSHOT
> artifacts
> >> of org.apache or codehaus?  This is causing a lot of builds issues in
> >>  GlassFish and other subprojects (JavaMail, HK2 etc...)
> >>
> >>
> >> Also, isn't this a bug in Nexus?  Why does the maven-metadata.xml
> contain
> >> SNAPSHOT versions if I create a proxy with repository policy as
> "release".
> >> For example the URL for maven-enforcer-plugin artifact in the proxy
> >> created for  JBoss repo in GlassFish Nexus server:
> >>
> >>
> http://maven.glassfish.org/content/repositories/JBoss/org/apache/maven/plugins/maven-enforcer-plugin/
> >>
> >> It contains no artifacts but there is a maven-metatdata.xml for the
> >> SNAPSHOT versions.
> >>
> >> Is this a bug?
> >>
> >> Jane
> >>
> >>
> >>
> >> On 11/11/10 1:07 AM, Anders Hammar wrote:
> >>
> >>> I think the problem is that you're proxying one of the repo groups of
> >>> JBoss's Nexus instance. That one includes the

RE: maven-metadata containing SNAPSHOT versions when Nexus group references release proxy repo

[Nord, James]

Repo managers must be able to cope with this.  Where is the release only 
version of java.net?

/James

-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of 
Anders Hammar
Sent: 11 November 2010 11:10
To: Jane Young; Maven Users List
Cc: Bill Shannon
Subject: Re: maven-metadata containing SNAPSHOT versions when Nexus group 
references release proxy repo

I think that the main problem is that you're specying the repo as a release
repo. It's a mixed repo as it contains snapshots.

/Anders

On Thu, Nov 11, 2010 at 11:29, Jane Young  wrote:

>  If I create a proxy repo in Nexus with policy set as "release" and it's
> referencing the group repo that contains SNAPSHOTs.  Should the proxy repo
> contain SNAPSHOT artifacts?  No...  but the metadata contains the SNAPSHOT
> versions.  Isn't this a discrepancy?
>
> Furthermore, if the pom file is referencing this proxy repo and has a
> dependency on a maven plugin, maven will try to download the latest version
> that is defined in metadata and the build is going to fail since the
> SNAPSHOT artifact is not available.
>
> If this is not a bug, how do you work around it?
>
>
>
>
> On 11/11/10 2:16 AM, Anders Hammar wrote:
>
> The first repos are group repos. The latter one is just a repo. You can
> tell from the urls.
>
> If the group repo contains a snapshot proxy repo, it will contain snapshot
> info in the metadata. It's not a bug.
>
> /Anders
>
> On Thu, Nov 11, 2010 at 11:12, Jane Young  wrote:
>
>> Hi Anders,
>>
>> The reason GlassFish Nexus group repository is  referencing
>> http://repository.jboss.org/nexus/content/groups/public/  is because it
>> contains specific glassfish  versions of Weld artifacts.
>> See:
>>
>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/weld-osgi-bundle/
>> vs
>>
>> http://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/weld/weld-osgi-bundle/
>>
>> Also, the repository is recommended by Pete Muir (Weld project lead).
>>
>> Is there another JBoss repository that does not contain SNAPSHOT artifacts
>> of org.apache or codehaus?  This is causing a lot of builds issues in
>>  GlassFish and other subprojects (JavaMail, HK2 etc...)
>>
>>
>> Also, isn't this a bug in Nexus?  Why does the maven-metadata.xml contain
>> SNAPSHOT versions if I create a proxy with repository policy as "release".
>> For example the URL for maven-enforcer-plugin artifact in the proxy
>> created for  JBoss repo in GlassFish Nexus server:
>>
>> http://maven.glassfish.org/content/repositories/JBoss/org/apache/maven/plugins/maven-enforcer-plugin/
>>
>> It contains no artifacts but there is a maven-metatdata.xml for the
>> SNAPSHOT versions.
>>
>> Is this a bug?
>>
>> Jane
>>
>>
>>
>> On 11/11/10 1:07 AM, Anders Hammar wrote:
>>
>>> I think the problem is that you're proxying one of the repo groups of
>>> JBoss's Nexus instance. That one includes the apache snapshots, which is
>>> intentional:
>>> http://community.jboss.org/message/564903#564903
>>>
>>> Instead, proxy the appropriate release repos. The jboss repo group
>>> 'public'
>>> also proxies Maven central I believe, which you don't want.
>>>
>>> There's info about the new nexus instance at JBoss at the JBoss blog:
>>> http://community.jboss.org/en/build/blog
>>> You should be able to find info there regarding which repos you should
>>> proxy.
>>>
>>> /Anders
>>>
>>> On Thu, Nov 11, 2010 at 00:00, Jane Young  wrote:
>>>
>>>  I'm not sure if this is the right forum to post this question.  If not,
  please advice me where to post this question.

 I setup a Nexus group repository that references several proxy
 repositories.   This group repo only references the released
 (non-SNAPSHOT)
 artifacts.

 The group repo references: JBoss Maven repo and  Maven central repo.
 The JBoss Maven repo contains SNAPSHOT artifacts (e.g.

 https://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-enforcer-plugin/
 )

 and Maven central repo contains released versions (e.g.

 http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/
 )

 The group repo should only contain the released version from Maven
 central:
 See:

 http://maven.glassfish.org/content/groups/glassfish/org/apache/maven/plugins/maven-enforcer-plugin/

 However, the maven-metadata.xml file contains both SNAPSHOT and
 non-SNAPSHOT:


 http://maven.glassfish.org/content/groups/glassfish/org/apache/maven/plugins/maven-enforcer-plugin/maven-metadata.xml

 This is creating some problem in our build since some of pom file do not
 include the version of the plugin, so maven will try to download the
 latest
 version, which is a SNAPSHOT version but the group repo does not have
 the
 SNAPSHOT artifact.

 Is this a bug?  I have tried rebuilding metadata but it still contains
 SN

RE: maven-metadata containing SNAPSHOT versions when Nexus group references release proxy repo

[Nord, James]

Or upgrade to 1.8.0

https://issues.sonatype.org/browse/NEXUS-3729

/James

-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of 
Anders Hammar
Sent: 11 November 2010 09:07
To: Maven Users List
Subject: Re: maven-metadata containing SNAPSHOT versions when Nexus group 
references release proxy repo

I think the problem is that you're proxying one of the repo groups of
JBoss's Nexus instance. That one includes the apache snapshots, which is
intentional:
http://community.jboss.org/message/564903#564903

Instead, proxy the appropriate release repos. The jboss repo group 'public'
also proxies Maven central I believe, which you don't want.

There's info about the new nexus instance at JBoss at the JBoss blog:
http://community.jboss.org/en/build/blog
You should be able to find info there regarding which repos you should
proxy.

/Anders

On Thu, Nov 11, 2010 at 00:00, Jane Young  wrote:

> I'm not sure if this is the right forum to post this question.  If not,
>  please advice me where to post this question.
>
> I setup a Nexus group repository that references several proxy
> repositories.   This group repo only references the released (non-SNAPSHOT)
> artifacts.
>
> The group repo references: JBoss Maven repo and  Maven central repo.
> The JBoss Maven repo contains SNAPSHOT artifacts (e.g.
> https://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-enforcer-plugin/
> )
>
> and Maven central repo contains released versions (e.g.
> http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/
> )
>
> The group repo should only contain the released version from Maven central:
> See:
> http://maven.glassfish.org/content/groups/glassfish/org/apache/maven/plugins/maven-enforcer-plugin/
>
> However, the maven-metadata.xml file contains both SNAPSHOT and
> non-SNAPSHOT:
>
> http://maven.glassfish.org/content/groups/glassfish/org/apache/maven/plugins/maven-enforcer-plugin/maven-metadata.xml
>
> This is creating some problem in our build since some of pom file do not
> include the version of the plugin, so maven will try to download the latest
> version, which is a SNAPSHOT version but the group repo does not have the
> SNAPSHOT artifact.
>
> Is this a bug?  I have tried rebuilding metadata but it still contains
> SNAPSHOT versions.
> Is there a workaround?
>
> Thanks,
> Jane
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: Maven wants to get plugin versions that don't exist

[Nord, James]

See http://maven.40175.n5.nabble.com/settings-xml-td131025.html#a131025

/James

-Original Message-
From: Phillip Hellewell [mailto:ssh...@gmail.com]
Sent: 21 October 2010 16:09
To: Maven Users List
Subject: Re: Maven wants to get plugin versions that don't exist

On Thu, Oct 21, 2010 at 9:04 AM, Nord, James  wrote:
> https://issues.sonatype.org/browse/NEXUS-3729 ?
>
> Fixed in 1.8+

I'm not sure if that's exactly what it is, but it sounds similar.

I just removed "Apache Snapshots" and "Codehaus Snapshots" from my
Public Repositories group and now all is well, hooray!

Now tell me, why would Nexus put these snapshot repos in my Public
Repositories group by default?  That's just insane, or am I missing
something?  (Sorry, this complaint should be on the Nexus list).

Phillip

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Maven wants to get plugin versions that don't exist

[Nord, James]

https://issues.sonatype.org/browse/NEXUS-3729 ?

Fixed in 1.8+

/James

-Original Message-
From: Phillip Hellewell [mailto:ssh...@gmail.com]
Sent: 21 October 2010 15:53
To: Maven Users List
Subject: Re: Maven wants to get plugin versions that don't exist

On Thu, Oct 21, 2010 at 8:38 AM, Joachim Van der Auwera
 wrote:
> Sounds familiar.
> I have seen these problems occur because of inclusion of the JBoss maven
> repo.
> In my case, I fixed it by not proxying the entire jboss repo but only there
> releases.

Hmm, I don't see a JBoss repo in my Nexus, however I do see an Apache
Snapshots.  I shouldn't have that in there should I?  Hmm, there's
also Codehaus Snapshots.  I don't think I want that either.

General question about plugins: Is it true that running a plugin
(e.g., mvn help:help) will choose the latest version even if it is a
snapshot?  That seems kind of, I don't know, not good.  Why not let
the developers of the plugin have to specify a version to run for a
snapshot, and let the rest of us run the latest _release_ version?

Phillip

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Getting a useful Manifest

[Nord, James]

With subversion you don't know the version of what you are building if you have 
made local modifications until you merge and checkin.

The following works for me without hitting the repo (but it does run the svn 
command)


org.codehaus.mojo
buildnumber-maven-plugin
1.0-beta-1


validate

create




false
false





-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: 20 August 2010 14:20
To: users@maven.apache.org
Subject: Re: Getting a useful Manifest

  Tried to use it but could never get the SCM configuration to work.
I use Eclipse to access svn and I am not sure I want Maven doing
anything there in any event.

I want the version number of what I am building not the build of what is
currently on the subversion repo.
I am not sure what the plug-in is going to do with info from the repo. I
did turn of DoUpdate and DoCheck but it still wanted to go to the repo
for something.

The SCM stuff seems a bit hard to understand. I tried many variations of
what Eclipse is using but never found a configuration that Maven liked.

http://maven.apache.org/scm/maven-scm-plugin/usage.html seemed the most
useful page along with
http://maven.apache.org/scm/subversion.html
but no joy.

I may come back to this later when I have more time for head banging.

Thanks

Ron



On 20/08/2010 8:25 AM, Nord, James wrote:
> Take a look at the BuildNumber[1] plugin
>
> The date will be the timestamp of the actual file - do you need to get this 
> or can you use the file time?
>
> /James
>
> [1] http://mojo.codehaus.org/buildnumber-maven-plugin/
>
> -Original Message-
> From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
> Sent: 20 August 2010 13:07
> To: users@maven.apache.org
> Subject: Re: Getting a useful Manifest
>
>PluginManagement works well.
> It took a lot of trial and error to get a working split between the
> information in the parent's plug-in management and the module's plug-in
> description.
>
> There are 2 things that I would like to add.
> The first is the date that the manifest was made.
> The second is the SCM (subversion in my case) version number.
>
> Any ideas about how to get those into the Manifest?
>
> This is the current setup that works
> I put the following in the Parent POM
> 
> 
> 
> org.apache.maven.plugins
> maven-assembly-plugin
> 2.2-beta-5
> 
> 
> package
> 
> single
> 
>
> 
> 
> 
> true
> true
> 
> 
> 
> 
>   jar-with-dependencies
> 
> 
>
> 
> 
> 
> 
>
> 
> 
>
> and the following in the module
> 
> 
> 
> org.apache.maven.plugins
> maven-assembly-plugin
> 
> 
> 
>
> This produced a nice MANIFEST.MF with the following:
> Manifest-Version: 1.0
> Archiver-Version: Plexus Archiver
> Created-By: Apache Maven
> Built-By: rwheeler
> Build-Jdk: 1.6.0_17
> Specification-Title: Spring
> Specification-Version: 1.9.1
> Specification-Vendor: Artifact Software
> Implementation-Title: Spring
> Implementation-Version: 1.9.1
> Implementation-Vendor-Id: com.artifact_software.lms
> Implementation-Vendor: Artifact Software
>
>
>
>
>
> On 19/08/2010 4:08 PM, Ron Wheeler wrote:
>>   The instructions worked beautifully.
>>
>> Now I have a lot of POMS to modify unless I can add something to my
>> parent pom that will modify the plug-ins in my module poms.
>> In my modules I have this:
>> 
>> maven-assembly-plugin
>> 2.2-beta-2
>> 
>> 
>> create-Jasper-jar
>> package
>> 
>> single
>> 
>> 
>> 
>> 
>>jar-with-dependencies
>> 
>> 
>> 
>> 
>> 
>> 
>> I would like it to include :
>> 
>> 
>> true
>> true
>> 
>> 
>> to effectively become this:
>> maven-assembly-plugin
>> 2.2-beta-2
>> 
>> 
>> package
>> 
>> single
>> 
>> 
>> 
>> 
>> true
>> true
>> 
>> 
>> 
>> 
>>jar-with-dependencies
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> Any way to get the parent pom to supply a bit of the plug-in
>> configuration?
>>
>>
>> On 19/08/2010 11:43 AM, Anders Hammar wrote:
>>> But you'll file a 

RE: Getting a useful Manifest

[Nord, James]

Take a look at the BuildNumber[1] plugin

The date will be the timestamp of the actual file - do you need to get this or 
can you use the file time?

/James

[1] http://mojo.codehaus.org/buildnumber-maven-plugin/

-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: 20 August 2010 13:07
To: users@maven.apache.org
Subject: Re: Getting a useful Manifest

  PluginManagement works well.
It took a lot of trial and error to get a working split between the
information in the parent's plug-in management and the module's plug-in
description.

There are 2 things that I would like to add.
The first is the date that the manifest was made.
The second is the SCM (subversion in my case) version number.

Any ideas about how to get those into the Manifest?

This is the current setup that works
I put the following in the Parent POM



org.apache.maven.plugins
maven-assembly-plugin
2.2-beta-5


package

single





true
true




 jar-with-dependencies











and the following in the module



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




This produced a nice MANIFEST.MF with the following:
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: rwheeler
Build-Jdk: 1.6.0_17
Specification-Title: Spring
Specification-Version: 1.9.1
Specification-Vendor: Artifact Software
Implementation-Title: Spring
Implementation-Version: 1.9.1
Implementation-Vendor-Id: com.artifact_software.lms
Implementation-Vendor: Artifact Software





On 19/08/2010 4:08 PM, Ron Wheeler wrote:
>  The instructions worked beautifully.
>
> Now I have a lot of POMS to modify unless I can add something to my
> parent pom that will modify the plug-ins in my module poms.
> In my modules I have this:
> 
> maven-assembly-plugin
> 2.2-beta-2
> 
> 
> create-Jasper-jar
> package
> 
> single
> 
> 
> 
> 
>   jar-with-dependencies
> 
> 
> 
> 
> 
> 
> I would like it to include :
> 
> 
> true
> true
> 
> 
> to effectively become this:
> maven-assembly-plugin
> 2.2-beta-2
> 
> 
> package
> 
> single
> 
> 
> 
> 
> true
> true
> 
> 
> 
> 
>   jar-with-dependencies
> 
> 
> 
> 
> 
> 
>
> Any way to get the parent pom to supply a bit of the plug-in
> configuration?
>
>
> On 19/08/2010 11:43 AM, Anders Hammar wrote:
>> But you'll file a ticket to get this fixed, right?
>>
>> /Anders (mobile)
>>
>> Den 2010 8 19 17:36 skrev "Ron Wheeler":
>>> http://maven.apache.org/shared/maven-archiver/examples/manifest.html
>>> Has a better description of how the mapping is done.
>>>
>>> Not sure why
>>> http://maven.apache.org/guides/mini/guide-manifest.html
>>> does not provide a link.
>>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

Maven 3 - site plugin?

[Nord, James]

Hi all,

Does the new site plugin pick up the config for the reporting plugins from 
plugin management or build section?

That is with maven 2 if I want to have a checkstyle report in the project site 
but also be able to generate it from the command line "mvn 
checkstyle:checkstyle" I need to configure checkstyle twice, once in the 
 section and once in the build/plugins section.  Is this still the 
case with Maven3 and the inline configuration of the site plugin?  If not what 
do I configure to only need to configure checkstyle the once?

Regards,

/James

-Original Message-
From: Olivier Lamy [mailto:ol...@apache.org]
Sent: 10 August 2010 23:26
To: Maven Users List; annou...@maven.apache.org
Cc: Maven Developers List
Subject: [ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3

The Maven team is pleased to announce the release of the Maven Site
Plugin, version 3.0-beta-1 for Maven 3.
This version is intended to be the first version of the Maven Site
Plugin for Maven 3 and it currently only works with Apache Maven
3.0-beta-2.

The Site Plugin is used to generate a site for the project. The
generated site also includes the project's reports that were configured
in the  section of the POM.

The 3.x version of the Site Plugin has changed the way you configure
reports. You can read more about the new configuration mode at [1].

You should specify the version in the  section of your project's POM:


 org.apache.maven.plugins
 maven-site-plugin
 3.0-beta-1


Release Notes - Maven Site Plugin - Version 3.0-beta-1

Bug
MSITE-456 - regression Site navigation not generated
MSITE-460 - error when using Maven 3.x with maven-site-plugin 3.x
MSITE-477 -  href's drop the leading character in
the href when staging a site
MSITE-490 - WARNING Deprecated API called - not
org.apache.maven.doxia.sink.Sink instance and no SinkFactory
available. Please update this plugin.

Improvement
MSITE-436 - regenerate every page when site.xml (direct or parent) is changed
New Feature
MSITE-463 - Lithuanian translation
MSITE-465 - Add a site:effective-site goal (similar to help:effective-pom)

Task
MSITE-478 - Attach site descriptor as an artifact, not metadata, to the project
MSITE-482 - Update to Doxia 1.1.3
MSITE-487 - upgrade source to java 5

Users interested in testing this beta release should have a glance at
the compatibility notes for known differences between Maven 3.0 and
Maven 2.x:
https://cwiki.apache.org/confluence/x/sokr


Know limitations :
* deployment vith dav currently doesn't work.

You must note that the default execution of site:attach-descriptor has
been removed from the built-in lifecycle bindings for projects with
packaging "pom".
So now, you have to define the following goal execution to restore the
intended behavior:


  
maven-site-plugin
3.0-beta-1

  
attach-descriptor

  attach-descriptor

  

  


On the wiki page [2], you will find more information on how to
configure your POM in order to be able to continue building site with
both Maven 2.x and Maven 3.

You must note this version is a beta. You will find more informations
on migration [4]

--
The Maven  Team

[1] https://cwiki.apache.org/confluence/x/sokr Section "New Configuration"
[2] https://cwiki.apache.org/confluence/x/sokr Section "Using
maven-site-plugin 2.x with Maven 2.x and maven-site-plugin 3.x with
Maven 3.x"
[4] https://cwiki.apache.org/confluence/x/hQ1kAQ


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: Command line output when running JUnit 4 test suite

[Nord, James]

Peter,

Could it be you have redirectTestOutputToFile set to true?

http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile

/James

-Original Message-
From: Peter Niederwieser [mailto:pnied...@gmail.com]
Sent: 06 June 2010 22:22
To: users@maven.apache.org
Subject: Re: Command line output when running JUnit 4 test suite



klauer wrote:
>
> The Maven Surefire plugin allows you to explicitly set a single test or
> set of tests using wildcard matching:
>
I'm aware of -Dtest, but that's not what I want.


klauer wrote:
> And as for your "better command line output",  why not just use the
> command line
> to output the test right there:
> mvn test -Dtest=MyTest; cat
> target/surefire-reports/com.thingMyTest.txt
>
This will only give me feedback (plus lots of noise) once the whole suite
has completed, which is exactly what I'm trying to avoid.

Cheers,
Peter

--
View this message in context: 
http://old.nabble.com/Command-line-output-when-running-JUnit-4-test-suite-tp28786362p28793392.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: release plugin issues.

[Nord, James]

Oops that's embarrassing :-0

Meant to elsewhere...

/James

-Original Message-
From: Nord, James [mailto:jn...@nds.com]
Sent: 14 May 2010 18:10
To: Maven Users List
Subject: release plugin issues.

Hi all,

The reason we seem to need to do a build of a snapshot version before 
performing a release may be due to this issue:

http://jira.codehaus.org/browse/MRELEASE-3

This is apparently fixed in the version after the version of the release 
plug-in we are using in CAB Build.

It is easy enough for us to upgrade the plug-in version for VAM only and put it 
through its paces to see if that fixes it - but I'm short on time at the moment 
to see if that really fixes the issue - and the real issue is the build takes 
way to long (otherwise waiting a short amount of time for the build would be a 
non issue)...

/James



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

release plugin issues.

[Nord, James]

Hi all,

The reason we seem to need to do a build of a snapshot version before 
performing a release may be due to this issue:

http://jira.codehaus.org/browse/MRELEASE-3

This is apparently fixed in the version after the version of the release 
plug-in we are using in CAB Build.

It is easy enough for us to upgrade the plug-in version for VAM only and put it 
through its paces to see if that fixes it - but I'm short on time at the moment 
to see if that really fixes the issue - and the real issue is the build takes 
way to long (otherwise waiting a short amount of time for the build would be a 
non issue)...

/James



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: No such archiver: 'swf'.

[Nord, James]

I do pretty much the same but specify the group and artifact of the swf (not 
classifier or type) and it works, so that may give you a workaround requiring 
no coding.

/James
-Original Message-
From: Jörg Schaible [mailto:joerg.schai...@gmx.de]
Sent: 14 May 2010 16:15
To: users@maven.apache.org
Subject: Re: No such archiver: 'swf'.

Brian Fox wrote:

> Take a look at the patch for this issue:
> http://jira.codehaus.org/browse/MDEP-183
>
> You would need to do something along the same lines, possibly
> introducing your own archiver impl, but this shows how you map the
> extension to the impl.

Shouldn't the flex mojo already declare in its own component.xml this
unarchiver and all that is necessary for the dependency-plugin is an
true configuration?

- Jörg



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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: What MavenProject.getCollectedProjects() return

[Nord, James]

http://maven.apache.org/ref/2.2.1/maven-project/apidocs/


-Original Message-
From: Jimi Hullegård [mailto:jimi.hulleg...@mogul.com]
Sent: 16 April 2010 14:19
To: Maven Users List
Subject: SV: What MavenProject.getCollectedProjects() return

Is it just me that thinks it's a bit strange that this javadoc isn't published 
on the Documentation part of the regular Maven site?

/Jimi


Från: Marshall Schor [...@schor.com]
Skickat: den 16 april 2010 14:49
Till: Maven Users List
Ämne: Re: What MavenProject.getCollectedProjects() return

This can be found in the main maven repository, here:

http://repo2.maven.org/maven2/org/apache/maven/maven-project

pick the version you want, and then follow that link to the jar,
javadocs, and sources

-Marshall Schor

On 4/15/2010 5:29 AM, amaresh mourya wrote:
> Hi All,
>
> Can somebody point me the location/link where I can have doc for this method
> :  MavenProject.getCollectedProjects()
>
> Thanks,
> Amaresh
>
>

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



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes.
To protect the environment please do not print this e-mail unless necessary.

An NDS Group Limited company. www.nds.com

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

How to share a similar file across modules?

[Nord, James]

Hi all,

I have a file that will be 99% the same that will be used by many modules.

My original idea was to use the maven remote resources plugin with filtering to 
achieve my aims only this achieves only part of the need (only one place holds 
the file so updates are consistent & filtering can be done on the file to 
achieve the customization that is needed).

However the other part of the need is that the file needs to be named 
differently on each usage - and I am stuck as to how I might accomplish that?

Does anyone have any ideas / pointers that would help - or do I need to write a 
custom mojo for this?

An example of the usage would be


* A Shared component has a generic init.d script in 
src/main/resources/init.d_script

* This would have a placeholder ${project.properties.mainClass} in the 
line that launches java

* The name of the init.d script needs to be different by all users.

Regards,

/James



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**


This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes.
To protect the environment please do not print this e-mail unless necessary.

An NDS Group Limited company. www.nds.com

RE: Super pom / enforcer issues?

[Nord, James]

Comments inline.

Regards,

/James


>>2009/12/9 Nord, James :
>> I'm having a really strange error in Maven 2.2.1 and the enforcer plugin.
>>
>> Basically it appears as though the super pom is missing version definitions 
>> for the following even though they should be present according to the web 
>> documentation (and performing a help:effective-pom shows them listed in the 
>> pluginManagement section):
>> *   maven-clean-plugin
>> *   maven-deploy-plugin
>> *   maven-install-plugin
>> *   maven-site-plugin
>>
>> Anyone any ideas what's happening?

>If I read your mail correctly then you're thinking the Enforcer plugin
>should not complain about missing versions if those versions are
>provided by the super pom.

Correct.

>But think about it, if you upgrade to a
>newer Maven version then you could get a different super pom and as
>such your build is not reproducible.

But the build is reproducible - you made an invalid assumption.  In our builds 
we record the Maven version used to do the build so if we want to reproduce it 
we use exactly the same maven version on exactly the same platform with exactly 
the same JDK.
I don't expect any maven version to give exactly the same results as a 
different version.

>You should explicitly list the versions of everything you use. Don't
>depend on the super pom to do it for you. The Enforcer plugin is just
>doing what you asked it to do.

From the documentation:
"The Super POM is Maven's default POM. All POMs extend the Super POM unless 
explicitly set"

"This rule enforces that all plugins have a version defined, either in the 
plugin or pluginManagement section of the pom or a parent pom."

The combination of the two says to me that my POM implicitly has the Super POM 
as its parent, and hence *does* have the versions defined.

My take on the Enforcer plugin is to make builds reproducible given the same 
environment at a latter date.  Changing Maven version (or JDK!) changes the 
environment and is out of scope IMHO.  This is especially the case if you 
explicitly limit the version of Maven and JDK (and OS!) used in the enforcer 
rules, and setting these does make sure your build is reproducible.





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes.
To protect the environment please do not print this e-mail unless necessary.

An NDS Group Limited company. www.nds.com

Super pom / enforcer issues?

[Nord, James]

Hi all,

I'm having a really strange error in Maven 2.2.1 and the enforcer plugin.

Basically it appears as though the super pom is missing version definitions for 
the following even though they should be present according to the web 
documentation (and performing a help:effective-pom shows them listed in the 
pluginManagement section):
*   maven-clean-plugin
*   maven-deploy-plugin
*   maven-install-plugin
*   maven-site-plugin

Anyone any ideas what's happening?

> mvn validate
[INFO] Scanning for projects...
[INFO] 
[INFO] Building example
[INFO]task-segment: [validate]
[INFO] 
[INFO] [enforcer:enforce {execution: enforce-rules}]
[INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for 
updates from central
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequirePluginVersions 
failed with message:
Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not 
allowed )
org.apache.maven.plugins:maven-clean-plugin.The version currently in use is 
2.3
org.apache.maven.plugins:maven-deploy-plugin.   The version currently in use is 
2.4
org.apache.maven.plugins:maven-install-plugin.  The version currently in use is 
2.3
org.apache.maven.plugins:maven-site-plugin. The version currently in use is 
2.0.1
Found plugins without fixed release version defined.  Build is not reproducible.
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Some Enforcer rules have failed. Look above for specific messages 
explaining why the rule failed.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 4 seconds
[INFO] Finished at: Wed Dec 09 18:09:15 GMT 2009
[INFO] Final Memory: 6M/254M
[INFO] 

>mvn --version
Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
Java version: 1.6.0_16
Java home: C:\Java\jdk1.6.0_16\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"


-- begin pom.xml -

http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
example
myPom
0.0.1-SNAPSHOT
pom
example




maven-enforcer-plugin
1.0-beta-1


enforce-rules

enforce

validate





2.2.1





Found plugins without fixed release version defined.  Build is not 
reproducible.










-- end pom.xml -



  

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**



  
This message is confidential and intende

RE: Securing deployment of released artifacts

[Nord, James]

> I would like to ensure it is impossible to upload twice the 
> same artifact for a given project with a given non-SNAPSHOT 
> version and a given repository to upload to. I checked with 
> standard deploy plugin but this is not done (ie. I can upload 
> twice same version).
> 
> I checked with configuration parameters for nexus but could 
> not find anything related. Is there a standard way of doing this ?

http://nexus.sonatype.org/about/faq.html#QHowdoIdisableartifactredeploym
ent

Doesn't work with if you use staging though :-(

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

DefaultArtifact.getSelectedVersion throws N.P.E

[Nord, James]

WIth Maven 2.2.0 i'm getting an N.P.E from DefaultArtifact when calling
getSelectedVersion on a dependency.
 
This is in a multimodule project - and several modules build fine before
I hit the one that constantly failes.
 
[INFO] java.lang.NullPointerException
[INFO]  at
org.apache.maven.artifact.DefaultArtifact.getSelectedVersion(DefaultArti
fact.java:621)
[INFO]  at
com.nds.cab.build.enforcer.EngineeringReleaseRule.execute(EngineeringRel
easeRule.java:69)
[INFO]  at
org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:1
85)
[INFO]  at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:483)

The code in question (below) is an enforcer rule that does the following
- which looks ok to me.
 
Looking at the DefaultArtifact code there is the following comment
513
  // I am assuming this is happening as a
result of the MNG-1577 work, but somehow the value
514
  // of versionRange just goes null or is not
set. But this is happeningin Yoko and the value is
515
  // set when attaching the JAR and not set
when attaching the test JAR.
516
  if ( versionRange == null )
517
  {
518
  versionRange =
VersionRange.createFromVersion( version );
519
  }

However - the defaultArtifactHandler itself doesn't call getVersionRange
but uses the field diretly, which to me seems a little strange.

public void execute(EnforcerRuleHelper helper) throws
EnforcerRuleException {

   // the following results in a bogus POM during some phases //
MavenProject project = (MavenProject) helper.evaluate( "${project}" );
MavenSession session = (MavenSession) helper.evaluate("${session}");
MavenProject project = session.getCurrentProject(); Properties props =
session.getExecutionProperties(); if
(props.containsKey("skipEngineeringReleaseRule")) { log.warn("Skipping
EngineeringReleaseRule (user requested)"); } else if (
project.getArtifact().isSnapshot() ) { // snapshots can contain
engineering versions } else if
(isEngineeringVersion(project.getArtifact().getSelectedVersion())) { //
project is an engineering version so engineering versions are allowed! }
else { // we are a release version so check the dependencies for any
engineering release. log.info("Checking for engineering dependencies");
Set dependencies = project.getArtifacts(); 66: Iterator i =
dependencies.iterator(); 67: while (i.hasNext()) { 68: Artifact artifact
= (Artifact) i.next(); 69:if
(isEngineeringVersion(artifact.getSelectedVersion())) { 70: //
Engineering releases only come from NDS! 71: if
(artifact.getGroupId().startsWith("com.mycorp")) { throw new
EnforcerRuleException(ERROR_MSG); } } } } 
Am i doing somehting I'm not supposed to?  the quick and dirty is for me
to add a call to getVersionRange() before getSelectedVersion() but this
is masking the issue not nescesarily fixing it and if something deep
down is broken it doesn't leave me with a warm fuzzy feeling.
 
/James
 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Archetype plug-in and line end funnies.

[Nord, James]

So it is buggy then?

1) it should translate all CRLFs to LF (it doesn't, it only coverts
CRLFs in comments.)
2) it should really for convience replace all LFs to the platform
default encoding on writing.

It should be consistent - but it's not - it handles comments one way
(apparantly correctly but without 2) but not the rest of the document.

/James

> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
> Sent: 31 July 2009 09:31
> To: Maven Users List
> Subject: Re: Archetype plug-in and line end funnies.
> 
> See http://www.w3.org/TR/REC-xml/#NT-S
> 
> All CR characters are supposed to be removed from an XML file 
> when parsed.
> 
> -Stephen
> 
> 2009/7/30 Nord, James 
> 
> > Hi all,
> >
> > I've created an multi-module archetype and it seems to be working 
> > mostly well.  However any multi line comments in the poms 
> are getting 
> > written out as unix line ends and not Windows (which is what the 
> > platform and the original poms files are.)
> >
> > e.g
> >
> > CRLF
> >4.0.0CRLF
> > ...
> >  CRLF
> > ...
> > 
> >
> > gets written as
> > CRLF
> >4.0.0CRLF
> > ...
> >  CRLF
> > ...
> > 
> >
> > If I change the input file to be unix line ends then it all gets 
> > written as unix line ends - but I want it to be all written 
> using the 
> > native line end style (or CRLF if it can't do native).
> >
> > How do I achieve that - or is this an archetype bug (2.0-alpha4)
> >
> > /James
> >
> >
> > 
> **
> >  This message is confidential and intended only for 
> > the addressee. If you have received this message in error, please 
> > immediately notify the postmas...@nds.com and delete it from your 
> > system as well as any copies.
> > The content of e-mails as well as traffic data may be 
> monitored by NDS 
> > for employment and security purposes. To protect the environment 
> > please do not print this e-mail unless necessary.
> >
> > NDS Limited. Registered Office: One London Road, Staines, 
> Middlesex, 
> > TW18 4EX, United Kingdom. A company registered in England 
> and Wales. 
> > Registered no. 3080780. VAT no. GB 603 8808 40-00
> >
> > 
> **
> > 
> >
> 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

Archetype plug-in and line end funnies.

[Nord, James]

Hi all,
 
I've created an multi-module archetype and it seems to be working mostly
well.  However any multi line comments in the poms are getting written
out as unix line ends and not Windows (which is what the platform and
the original poms files are.)
 
e.g
 
CRLF
4.0.0CRLF
...
 CRLF
...

 
gets written as
CRLF
4.0.0CRLF
...
 CRLF
...

 
If I change the input file to be unix line ends then it all gets written
as unix line ends - but I want it to be all written using the native
line end style (or CRLF if it can't do native).  
 
How do I achieve that - or is this an archetype bug (2.0-alpha4)
 
/James 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Archetype: escaping velocity properties.

[Nord, James]

Thanks Jesse,

Worked like a charm.

/James 

> -Original Message-
> From: jie...@gmail.com [mailto:jie...@gmail.com] 
> Sent: 28 July 2009 13:24
> To: Maven Users List
> Subject: Re: Archetype: escaping velocity properties.
> 
> Hi James,
> 
> I place the following at the top of all my velocity-processed 
> resources:
> 
> #set( $symbol_pound = '#' )
> #set( $symbol_dollar = '$' )
> #set( $symbol_escape = '\' )
> 
> And then simply use those whenever I'd want to use the real 
> symbol, which is special to velocity. This works for me in 
> resources, remote-resources, and archetypes.
> 
> -jesse
> 
> On Tue, Jul 28, 2009 at 6:33 AM, Nord, James wrote:
> >
> > I'm creating an archetype but I need to escape some values so that 
> > velocity doesn't complain about them or even try and substitute them
> >
> 
> --
> There are 10 types of people in this world, those that can 
> read binary and those that can not.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

Archetype: escaping velocity properties.

[Nord, James]

Hi all,
 
I'm creating an archetype but I need to escape some values so that
velocity doesn't complain about them or even try and substitute them
 
However I tried \${value} as recommended in [1] but this gets put in the
final pom as "\${value}"  and not "${value}"
 
How do you escape these values so you can end up with ${value} in the
final pom that is generated from an archetype?
 
The only thing I could find was MRESOURCES-29 [2] but this seems to be
specifically for the resources plugin and not relevant to the Archetype
plugin.
 
/James
 
[1]
http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#
escapingvalidvtlreferences
[2] http://jira.codehaus.org/browse/MRESOURCES-29

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Prevent Install of Assembly

[Nord, James]

http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#attach 

> -Original Message-
> From: Jim Collings [mailto:jlistn...@gmail.com] 
> Sent: 23 July 2009 16:43
> To: Maven Users List
> Subject: Re: Prevent Install of Assembly
> 
> Didn't work. Neither did changing  to false.
> Anybody have additional ideas?
> 
> On Thu, Jul 23, 2009 at 11:25 AM, Jim 
> Collings wrote:
> > http://maven.apache.org/plugins/maven-assembly-plugin/usage.html
> >
> > So the docs I found at the link above had this to say:
> >
> > "When the assembly is created it will use the assemblyId as the 
> > artifact's classifier and will attach the created assembly to the 
> > project and will be uploaded into the repository on an install and 
> > deploy goal.'
> >
> > So in theory all I have to do is change the assemblyId?
> >
> > I'll see if I can figure out how to do this and try a test.
> >
> > On Thu, Jul 23, 2009 at 11:18 AM, Jim 
> Collings wrote:
> >> So I have a sub module that has an assembly.  It is 
> associated with 
> >> the "package" goal. Each time I run install though, the zip file 
> >> created is placed in the repository. There is no need for 
> this.  How 
> >> can I prevent it?
> >>
> >>
> >> Jim C.
> >>
> >
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

RE: site.xml for parent/child site which are siblings

[Nord, James]

There is another problem In that the children don't inherit the parents 
site.xml correctly (or probably more accuratly the parents site.xml gets munged 
when it is deployed.)

E.g we have a corporate pom which defines a site.xml which contains 

However when this gets deployed the  has gone.  And as any 
multi-module project that has the corporate pom as its parent doesn't show the 
list of it's modules...  Also it's missing any comments that where inside it.  
Shouldn't the deploy deploy the descriptor as is?

E.g. the following:

http://maven.apache.org/DECORATION/1.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/DECORATION/1.0.0 
http://maven.apache.org/xsd/decoration-1.0.0.xsd";>



http://xxx.yyy/some/path/default.aspx"; />
http://xxx.yyy/some/other/path/default.aspx"; />








 


Becomes

  
  

  http://xxx.yyy/some/path/default.aspx"; />
  http://xxx.yyy/some/other/path/default.aspx"; />


  



  


Note that reports have gone and the name is now hard coded?

/James

> -Original Message-
> From: Benson Margulies [mailto:bimargul...@gmail.com] 
> Sent: 16 July 2009 00:29
> To: Maven Users List
> Subject: Re: site.xml for parent/child site which are siblings
> 
> I never attached the workaround to the JIRA. It is MSITE-409. 
> I'm trying to get organized to try to fix it. However, the 
> whole idea of a 'parent' link needs thought.
> 
> On Wed, Jul 15, 2009 at 2:54 PM, David C. 
> Hicks wrote:
> > Benson Margulies wrote:
> >> I've filed a JIRA on this and also posted a workaround, 
> you have to 
> >> set up the URL for each project yourself. If you can't 
> find my posted 
> >> workaround I can post it again.
> >>
> > Benson, can you give us a JIRA number?  I didn't find anything that 
> > appeared to be the right one *and* had a workaround posted. 
>  I could 
> > have overlooked it, though.
> > Thanks!
> >
> >
> > 
> -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

release plugin?

[Nord, James]

Hi all,
 
Why if I specify exactly what versions to use for release and
developement version for the exact module and specify the default values
does the release plugin still try (and fail) to parse the versions?
 
e.g.
 
mvn.bat -B -X -e -Dproject.dev.test:test=X_1.0.1-SNAPSHOT
-Dproject.rel.test:test=X_1.0.0 -DdevelopmentVersion=BOGUS
-DreleaseVersion=BOGUS release:prepare 
 
(this is a single module project groupID=test artifactId=test)
 
Apache Maven 2.1.0 (r755702; 2009-03-18 19:10:27+)
Java version: 1.6.0_06
maven-release-plugin:2.0-beta-9
 
 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error parsing
version, cannot determine next version: Unable to
parse the version string: "X1.0.0-SNAPSHOT"
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:703)
...
Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing
version, cannot determine next version: Unable
to parse the version string: "X1.0.0-SNAPSHOT"
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRelea
seMojo.java:186)
...
Caused by: org.apache.maven.shared.release.ReleaseExecutionException:
Error parsing version, cannot determine next versi
on: Unable to parse the version string: "X1.0.0-SNAPSHOT"
at
org.apache.maven.shared.release.phase.MapVersionsPhase.getNextVersion(Ma
pVersionsPhase.java:227)
at
org.apache.maven.shared.release.phase.MapVersionsPhase.execute(MapVersio
nsPhase.java:140)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultRel
easeManager.java:196)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultRel
easeManager.java:133)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultRel
easeManager.java:96)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRelea
seMojo.java:182)
... 18 more
Caused by:
org.apache.maven.shared.release.versions.VersionParseException: Unable
to parse the version string: "X1.0.0-SNAPSHOT"
at
org.apache.maven.shared.release.versions.DefaultVersionInfo.(Defau
ltVersionInfo.java:171)
at
org.apache.maven.shared.release.phase.MapVersionsPhase.getNextVersion(Ma
pVersionsPhase.java:177)
... 23 more
 
 
Fair enoguh if I haven't parsed in any versions as this version is in
effect just a string qualifier (which is a valid version?) - but I have
been explicit so what gives ?
 
Would this be considered as a bug or would it be rejected due to the
non-standard version.
 
Regards,
 
/James
 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: plugin search?

[Nord, James]

I didn't want to enforce it just be able to run "mvn baddeps:analyze" and have 
it tell me in a more obvious way than I can see at the 
Moment (and I'm talkin about non transitive dependencies).

e.g

mvn baddeps:analyze

Project B,Project C both declare a dependency on com.foo.bar:bax:1.0.1  
consider using dependecyManagement.
*** Project D,Project E use incosistent versions of com.foo.bar:whizbang 
(1.0.1, 1.0.4) ***

And if there was mvn baddeps:fix_it then all the better - but the first part is 
more important to me (being able to see it obviously)

Anyway - at least my question is answered - doesn't seem like there is anything 
that can do this at the moment.

/James

> 
> My answer is always that if you want to enforce something... 
> use the enforcer.
> 
> Once I get 1.0 out the door I will be splitting out one or 
> two versions-api and versions-impl which will probably be 
> added as dependencies of the enforcer-rules-impl so that we 
> can share common code.
> 
> In that respect I am not opposed to adding version-reporting 
> stuff to the versions plugin... but perhaps this is a use 
> case for the dependency plugin to have a report...
> 
> We should socialize where such a mojo should live.  I don't 
> want the versions-maven-plugin to have too big a scope at the 
> end of the day.
> 
> -Stephen
> 
> P.S.
> 
> I suspect it will be somthing like
> 
> versions-query-api
> 
> and
> 
> versions-change-api
> 
> To allow enforcer to only depend on the querying code
> 
> 2009/6/5 Nord, James 
> 
> > Hi Stephen,
> >
> > I didn't see any rules that would help for this situation ( 
> > 
> http://maven.apache.org/enforcer/enforcer-rules/index.html).  
> (without 
> > writing a custom rule)
> >
> > If some custom code needs to be written I would I think it 
> would fit 
> > better with the versions-maven-plugin?
> >
> > /James
> >
> > > -Original Message-
> > > From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> > > Sent: 05 June 2009 11:41
> > > To: Maven Users List
> > > Subject: Re: plugin search?
> > >
> > > I think the enforcer plugin has rules to help.
> > >
> > > 2009/6/5 Martin Höller 
> > >
> > > > Hi!
> > > >
> > > > On Friday 05 June 2009 Nord, James wrote:
> > > > > Is there a plugin that anoyone knows that can analyse
> > > dependencies
> > > > > in a multi module project and then warn if you have a
> > > depenendency
> > > > > on the same artifact with a set version (ie not using
> > > > > dependencyManagement) in more than one project?
> > > >
> > > > Sounds like a job for the versions-maven-plugin [0]. I 
> think the 
> > > > plugin already warns you if dependencyManagement is not
> > > used. Not sure
> > > > about different versions. If it doesn't support you use
> > > case file an
> > > > enhancement request in JIRA. Maybe Stephen Connolly can
> > > provide some more details.
> > > >
> > > > hth,
> > > > - martin
> > > >
> > > > [0] http://mojo.codehaus.org/versions-maven-plugin/
> > > >
> > >
> >
> >
> > 
> **
> >  This message is confidential and intended only for 
> > the addressee. If you have received this message in error, please 
> > immediately notify the postmas...@nds.com and delete it from your 
> > system as well as any copies.
> > The content of e-mails as well as traffic data may be 
> monitored by NDS 
> > for employment and security purposes. To protect the environment 
> > please do not print this e-mail unless necessary.
> >
> > NDS Limited. Registered Office: One London Road, Staines, 
> Middlesex, 
> > TW18 4EX, United Kingdom. A company registered in England 
> and Wales. 
> > Registered no. 3080780. VAT no. GB 603 8808 40-00
> >
> > 
> **
> > 
> >
> > 
> -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 

**
This message is confidential and intended only for the addressee. If you have 
received this message i

RE: plugin search?

[Nord, James]

Hi Stephen,

I didn't see any rules that would help for this situation 
(http://maven.apache.org/enforcer/enforcer-rules/index.html).  (without writing 
a custom rule)

If some custom code needs to be written I would I think it would fit better 
with the versions-maven-plugin?

/James

> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
> Sent: 05 June 2009 11:41
> To: Maven Users List
> Subject: Re: plugin search?
> 
> I think the enforcer plugin has rules to help.
> 
> 2009/6/5 Martin Höller 
> 
> > Hi!
> >
> > On Friday 05 June 2009 Nord, James wrote:
> > > Is there a plugin that anoyone knows that can analyse 
> dependencies 
> > > in a multi module project and then warn if you have a 
> depenendency 
> > > on the same artifact with a set version (ie not using 
> > > dependencyManagement) in more than one project?
> >
> > Sounds like a job for the versions-maven-plugin [0]. I think the 
> > plugin already warns you if dependencyManagement is not 
> used. Not sure 
> > about different versions. If it doesn't support you use 
> case file an 
> > enhancement request in JIRA. Maybe Stephen Connolly can 
> provide some more details.
> >
> > hth,
> > - martin
> >
> > [0] http://mojo.codehaus.org/versions-maven-plugin/
> >
> 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

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

plugin search?

[Nord, James]

Hi all,
 
Is there a plugin that anoyone knows that can analyse dependencies in a
multi module project and then warn if you have a depenendency on the
same artifact with a set version (ie not using dependencyManagement) in
more than one project?
 
ie
 
+ root pom.xml
 |-- project A 
 |   \ pom.xml (depenedency on foo:bar:1.0.0 , bar:bar:1.0.0)
 | 
 |-- project B
 |   \pom.xml (depnedency on foo:bar 1.0.0, joe:blogs:1.3.2)
 |
 |-- project C
 |   \pom.xml (dependency on joe:blogs:1.3.2, bob:dillon:4.3.2)
 
that is when run would on the root module would
 
1) warn about A and B both declaring foo:bar:1.0.0 (should be in
dependencyManagement of A)
2) warn very loudly about B and C both declaring joe:blogs but with
different versions (need to standardise on a version and use
dependencyManagement).
 
Regards,
 
/James
 
 
 

**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

sources attached twice during release:perform.

[Nord, James]

Hi all,
 
I recently updated to use the mave-source-plugin:2.1 with the following
config
 

  maven-source-plugin
  2.1
  

  attach-sources
  verify
  
jar-no-fork
test-jar-no-fork
  

  


 
this works as expceted for normal instals and deploys however when
running the release plugin it tries to attach the sources twice (which
fails as we have nexus setup to prevent re-deployments)
 
release plugin is set to the following inside pluginManagement

  maven-release-plugin
  2.0-beta-8
  
-DskipSCMCheck
  


My guess is this is being over-ridden by the super poms
"release-profile" and we have both the fork and no-fork sources being
attached.
 
So my question is how to disable this in either corporate pom (I don't
want to have to run mvn -P-release-profile release:perform) as I want
the updated release info - and anything that will occur in future
versions of maven that is needed.
 
/James

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

RE: Apache snapshot repository metadata incorrect.

[Nord, James]

Thanks Brian.

/James

> Thanks for finding that. It's been fixed now.
> 
> The old repo had some junk versions that were being proxied. 
> It's been cleaned out.
> 
> We schedule daily cleanups of the snapshots, leaving behind 3 
> copies for a minimum of 10 days, the snapshots are removed 
> when a release is published.
> 
> Otherwise, we don't have it setup to actively recreate the 
> metadata as under normal conditions it should be managed by 
> maven, but in situations like this it's certainly handy to 
> repair with a few clicks.
> 
> On May 1, 2009, at 12:09 PM, Nord, James wrote:
> 
> > Hi all,
> >
> > The metadata served by nexus for 
> > http://repository.apache.org/snapshots/
> > is incorrect for the archetype plugin.
> >
> > 
> (https://repository.apache.org/content/groups/snapshots/org/apache/mav
> > en
> > /plugins/maven-archetype-plugin/)
> >
> > metadata contains lots of snapshot versions but only 
> > 2.0-alpha-5-SNAPSHOT is available.  (and hence running mvn 
> > archetype:generate from the command line fails as it tries to get 
> > 12-SNAPSHOT
> >
> > /James
> >
> >  
> > -
> > 
> <https://repository.apache.org/content/groups/snapshots/org/apache/mav
> > en /plugins/maven-archetype-plugin/maven-metadata.xml#>   > xsi:schemaLocation="http://maven.apache.org/METADATA/1.0.0
> > http://maven.apache.org/xsd/metadata-1.0.0.xsd";
> > xmlns="http://maven.apache.org/METADATA/1.0.0";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> >  org.apache.maven.plugins
> >  maven-archetype-plugin
> >  2.0-alpha-4-SNAPSHOT
> > -
> > 
> <https://repository.apache.org/content/groups/snapshots/org/apache/mav
> > en /plugins/maven-archetype-plugin/maven-metadata.xml#>  
>   
> > 12-SNAPSHOT  
> > -
> > 
> <https://repository.apache.org/content/groups/snapshots/org/apache/mav
> > en /plugins/maven-archetype-plugin/maven-metadata.xml#>  
>   
> > 2.0-alpha-4-SNAPSHOT
> >  2.0-alpha-5-SNAPSHOT
> >  0.3.0-SNAPSHOT
> >  1.0-SNAPSHOT
> >  1.0-alpha-2-SNAPSHOT
> >  1.0-alpha-3-SNAPSHOT
> >  1.0-beta-3-SNAPSHOT
> >  1.0.2-SNAPSHOT
> >  1.1-SNAPSHOT
> >  1.1.1-SNAPSHOT
> >  1.2-SNAPSHOT
> >  1.2.2-SNAPSHOT
> >  1.3-SNAPSHOT
> >  2.0-beta-9-SNAPSHOT
> >  2.0-beta-10-SNAPSHOT
> >  2.0.11-SNAPSHOT
> >  2.1.0-SNAPSHOT
> >  2.1-SNAPSHOT
> >  2.1.0-M2-SNAPSHOT
> >  2.2-SNAPSHOT
> >  2.3-SNAPSHOT
> >  2.4.4-SNAPSHOT
> >  2.5-SNAPSHOT
> >  3.0-alpha-2-SNAPSHOT
> >  11-SNAPSHOT
> >  12-SNAPSHOT
> >  
> >  20090417213533
> >  
> >  
> >
> > 
> **
> >  This e-mail is confidential, the property 
> of NDS Ltd 
> > and intended for the addressee only. Any dissemination, copying or 
> > distribution of this message or any attachments by anyone 
> other than 
> > the intended recipient is strictly prohibited. If you have received 
> > this message in error, please immediately notify the 
> > postmas...@nds.com and destroy the original message. 
> Messages sent to 
> > and from NDS may be monitored. NDS cannot guarantee any message 
> > delivery method is secure or error-free. Information could be 
> > intercepted, corrupted, lost, destroyed, arrive late or 
> incomplete, or 
> > contain viruses. We do not accept responsibility for any errors or 
> > omissions in this message and/or attachment that arise as a 
> result of 
> > transmission.
> > You should carry out your own virus checks before opening any 
> > attachment. Any views or opinions presented are solely those of the 
> > author and do not necessarily represent those of NDS.
> >
> > To protect the environment please do not print this e-mail unless 
> > necessary.
> >
> > NDS Limited Registered Office: One London Road, Staines, Middlesex,
> > TW18 4EX, United Kingdom. A company registered in England and Wales 
> > Registered no. 3080780 VAT no. GB 603 8808 40-00
> > 
> **
> > 
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

**
This e-mail is confidenti

Apache snapshot repository metadata incorrect.

[Nord, James]

Hi all,
 
The metadata served by nexus for http://repository.apache.org/snapshots/
is incorrect for the archetype plugin.
 
(https://repository.apache.org/content/groups/snapshots/org/apache/maven
/plugins/maven-archetype-plugin/)
 
metadata contains lots of snapshot versions but only
2.0-alpha-5-SNAPSHOT is available.  (and hence running mvn
archetype:generate from the command line fails as it tries to get
12-SNAPSHOT
 
/James
 
   
-
  http://maven.apache.org/METADATA/1.0.0
http://maven.apache.org/xsd/metadata-1.0.0.xsd";
xmlns="http://maven.apache.org/METADATA/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  org.apache.maven.plugins 
  maven-archetype-plugin 
  2.0-alpha-4-SNAPSHOT 
-
  
  12-SNAPSHOT 
   
-
  
  2.0-alpha-4-SNAPSHOT 
  2.0-alpha-5-SNAPSHOT 
  0.3.0-SNAPSHOT 
  1.0-SNAPSHOT 
  1.0-alpha-2-SNAPSHOT 
  1.0-alpha-3-SNAPSHOT 
  1.0-beta-3-SNAPSHOT 
  1.0.2-SNAPSHOT 
  1.1-SNAPSHOT 
  1.1.1-SNAPSHOT 
  1.2-SNAPSHOT 
  1.2.2-SNAPSHOT 
  1.3-SNAPSHOT 
  2.0-beta-9-SNAPSHOT 
  2.0-beta-10-SNAPSHOT 
  2.0.11-SNAPSHOT 
  2.1.0-SNAPSHOT 
  2.1-SNAPSHOT 
  2.1.0-M2-SNAPSHOT 
  2.2-SNAPSHOT 
  2.3-SNAPSHOT 
  2.4.4-SNAPSHOT 
  2.5-SNAPSHOT 
  3.0-alpha-2-SNAPSHOT 
  11-SNAPSHOT 
  12-SNAPSHOT 
  
  20090417213533 
  
  

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

RE: Maven Overview Plugin version 1.4 has been released

[Nord, James]

> -Original Message-
> From: Rémy Sanlaville [mailto:remy.sanlavi...@gmail.com] 
> Sent: 09 April 2009 08:27
> To: Maven Users List
> Subject: Re: Maven Overview Plugin version 1.4 has been released
> 
> >
> > as long as the plugin has its own groupId, the artifactId 
> can be any thing.
> 
> 
> IMHO, even if the plugin has its own groupId, I agree with 
> Stephen that it's better to keep the convention :
> maven-_-plugin for o.a.m.p plugins
> _-maven-plugin for other plugins
> 

This was news to me to.  Is this documtented anywhere - prehaps it needs to be 
or made more prominent.

The only thing I could find from google (maven plugin naming conventions) was 
the following two pages neither of which stated this convention. 

http://www.sonatype.com/books/maven-book/reference/writing-plugins-sect-plugin-prefix.html

In other words, when the Maven Plugin Plugin is generating the Plugin 
descriptor for your plugin and you have not explicitly set the goalPrefix in 
your project, the plugin:descriptor goal will extract the prefix from your 
plugin's artifactId when it matches the following patterns: 
${prefix}-maven-plugin, OR 
maven-${prefix}-plugin


And 

http://maven.apache.org/guides/mini/guide-naming-conventions.html

Which mentions nothing...  It seems like although codehause standardised one 
_-maven-plugin and maven.a.o standardised on maven-__-plug-in other groups 
haven't standardised on either and they are all a mix

e.g.
maven-jetty-plug-in (org.mortbay.jetty)
tools-maven-plugin (org.apache.geronimo.genesis.plugins)
maven-jaxme-plug-in (org.apache.ws.jaxme)

(also try a quick search in nexus for *-maven-plug-in and maven-*-plug-in - and 
it looks like the hourse has bolted..)


/James

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

RE: Maven 2.1 and Maven 2.0.9 changes

[Nord, James]

Strange - I have exactly that and I just did a test with 2.1.0 and it
worked just the same as with 2.0.9

(mvn deploy of a snapshot version)


 
  
   com.nds.project 
   runtime 
   ${runtimeVersion} 
   import 
   pom 
  
 


Is it the core or a plug-in that is responsible for this?

/James 

> -Original Message-
> From: Brett Porter [mailto:br...@apache.org] 
> Sent: 08 April 2009 10:21
> To: Maven Users List
> Subject: Re: Maven 2.1 and Maven 2.0.9 changes
> 
> This change was by design in 2.1. You should be overriding 
> the version in the child by specifying the 
> dependencyManagement section again.
> 
> - Brett
> 
> On 08/04/2009, at 7:09 PM, Ben Storey wrote:
> 
> > Hi,
> >
> > We ran into a problem I thought I would make you aware of one of my 
> > colleagues was running maven 2.1 and we were all running maven 2.0.9
> >
> > When deploying with version 2.1.0 and you have properties 
> setup like 
> > the following in the root project.
> >
> > 
> >
> >  1.1
> >
> > 
> >
> > ...
> >
> > 
> >
> >  
> >
> >
> >
> >   commons-logging
> >
> >   commons-logging
> >
> >   ${commons-logging.version} 
> >
> >
> >
> >  
> >
> > 
> >
> >
> >
> > When you do the deploy with 2.0.9 it deploys like above, 
> however when 
> > deploying in 2.1. it substitutes the dependencyManagement version 
> > property like below.
> >
> >
> >
> > 
> >
> >  
> >
> >
> >
> >   commons-logging
> >
> >   commons-logging
> >
> >   1.1
> >
> >
> >
> >  
> >
> > 
> >
> >
> >
> > This means in the child projects we cannot override the 
> version by the
> > following:
> >
> >
> >
> > 
> >
> >  1.1.1
> >
> > 
> >
> >
> > Because maven does not do the substitution because there is no  
> > variable to
> > substitute in the root descriptor.
> >
> > With the way we are using maven currently the dependencyManagement  
> > elements
> > we want to be able to override some of our own library versions.
> >
> > Is this an enhancement or a bug?
> >
> > Cheers
> >
> > Ben
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

RE: SCM requires that command line svn be used?

[Nord, James]

Needed to also add should this be a dependency of the javadvn
implementation instead?


com.sun.jna
jna
3.0.5
 
/James

> -Original Message-
> From: Nord, James [mailto:jn...@nds.com] 
> Sent: 06 April 2009 17:28
> To: Maven Users List
> Subject: RE: SCM requires that command line svn be used?
> 
> Hi Oliver,
> 
> Is there any documentation on how to configure this.
> 
> Looking at the source I have tried adding the library as 
> dependencies to the scm plug-in and running
> 
> mvn -Dmaven.scm.provider.svn.implementation=javasvn scm:status 
> 
> However this fails to use stored local credentials and fails 
> with [INFO] [scm:status] [INFO] SVN status directory: 
> D:\workspaces\simpleProject\ [ERROR] Provider message:
> [ERROR] SVN status failed.
> [ERROR] Command output:
> [ERROR] svn: Authentication required for 
> '<https://svnrepo.myco.com:443> Welcome to My CO.s Subversion 
> Repository'
> 
> If I just run mvn scm:status it works fine - but uses svn.exe instead.
> 
> Authentication is configured in usual svn location for 
> windows %APPDATA%\Subversion and is in wincrypt form.
> 
> I have authentication present for multiple servers -however I 
> tried removing all but the one in question and it still fails.
> 
> /James
> 
> > -Original Message-
> > From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] 
> On Behalf 
> > Of Olivier Lamy
> > Sent: 26 March 2009 22:15
> > To: Maven Users List
> > Subject: Re: SCM requires that command line svn be used?
> > 
> > Hi,
> > It's possible with the javasvn implementation. This has been moved 
> > recently from the asf repository due to license issue.
> > Now it's here : http://code.google.com/p/maven-scm-provider-svnjava/
> > It will be released after the maven-scm release.
> > 
> > HTH,
> > --
> > Olivier
> > 
> > 2009/3/26 Chris :
> > > I'm trying to configure my pom to use an . We use 
> Subversion. 
> > > When I run it, I get the error "'svn' is not recognized as
> > an internal
> > > or external command, operable program or batch file.". I
> > take it this
> > > means that svn.exe needs to be on the path, and the plugin
> > is shelling out to access it.
> > >
> > > This is obviously flaky and error prone. In Ant, I can use
> > SvnAnt to
> > > access svn directly, using java alone.
> > >
> > > Is it possible to configure Maven to use one of the
> > svn-java libraries
> > > instead of the command line client?
> > >
> > >
> > > 
> > 
> -
> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: users-h...@maven.apache.org
> > >
> > >
> > 
> > 
> -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> > 
> > 
> 
> **
> 
> This e-mail is confidential, the property of NDS Ltd and 
> intended for the addressee only. Any dissemination, copying 
> or distribution of this message or any attachments by anyone 
> other than the intended recipient is strictly prohibited. If 
> you have received this message in error, please immediately 
> notify the postmas...@nds.com and destroy the original 
> message. Messages sent to and from NDS may be monitored. NDS 
> cannot guarantee any message delivery method is secure or 
> error-free. Information could be intercepted, corrupted, 
> lost, destroyed, arrive late or incomplete, or contain 
> viruses. We do not accept responsibility for any errors or 
> omissions in this message and/or attachment that arise as a 
> result of transmission. You should carry out your own virus 
> checks before opening any attachment. Any views or opinions 
> presented are solely those of the author and do not 
> necessarily represent those of NDS.
> 
> To protect the environment please do not print this e-mail 
> unless necessary.
> 
> NDS Limited Registered Office: One London Road, Staines, 
> Middlesex, TW18 4EX, United Kingdom. A company registered in 
> England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
> **
> 
> 
> 

RE: SCM requires that command line svn be used?

[Nord, James]

Hi Oliver,

Is there any documentation on how to configure this.

Looking at the source I have tried adding the library as dependencies to
the scm plug-in and running

mvn -Dmaven.scm.provider.svn.implementation=javasvn scm:status 

However this fails to use stored local credentials and fails with
[INFO] [scm:status]
[INFO] SVN status directory: D:\workspaces\simpleProject\
[ERROR] Provider message:
[ERROR] SVN status failed.
[ERROR] Command output:
[ERROR] svn: Authentication required for '
Welcome to My CO.s Subversion Repository'

If I just run mvn scm:status it works fine - but uses svn.exe instead.

Authentication is configured in usual svn location for windows
%APPDATA%\Subversion and is in wincrypt form.

I have authentication present for multiple servers -however I tried
removing all but the one in question and it still fails.

/James

> -Original Message-
> From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On 
> Behalf Of Olivier Lamy
> Sent: 26 March 2009 22:15
> To: Maven Users List
> Subject: Re: SCM requires that command line svn be used?
> 
> Hi,
> It's possible with the javasvn implementation. This has been 
> moved recently from the asf repository due to license issue.
> Now it's here : http://code.google.com/p/maven-scm-provider-svnjava/
> It will be released after the maven-scm release.
> 
> HTH,
> --
> Olivier
> 
> 2009/3/26 Chris :
> > I'm trying to configure my pom to use an . We use Subversion. 
> > When I run it, I get the error "'svn' is not recognized as 
> an internal 
> > or external command, operable program or batch file.". I 
> take it this 
> > means that svn.exe needs to be on the path, and the plugin 
> is shelling out to access it.
> >
> > This is obviously flaky and error prone. In Ant, I can use 
> SvnAnt to 
> > access svn directly, using java alone.
> >
> > Is it possible to configure Maven to use one of the 
> svn-java libraries 
> > instead of the command line client?
> >
> >
> > 
> -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

RE: filtering site resources?

[Nord, James]

Thanks,

Did something very similar that worked (below for future reference)..

/James



src/main/filters/filter.properties





org.apache.maven.plugins

maven-resources-plugin
2.3



site-filtering-hack
pre-site


copy-resources


false


${basedir}/target/site/runtime_docs




src/main/site-resources/runtime_docs

true





UTF-8








> -Original Message-
> From: EJ Ciramella [mailto:ecirame...@upromise.com] 
> Sent: 01 April 2009 18:23
> To: Maven Users List
> Subject: RE: filtering site resources?
> 
> Yeah, we struggled with this too - and being forced to only 
> use velocity properties was a deal breaker for us (all of our 
> properties are in the foo.bar style).
> 
> On a side project, I simply put site template files in the 
> resources directory and process them to the src/site 
> directory where I want them (so the foo.bar properties are 
> expanded).  Just make sure the clean plugin cleans this directory.
> 
> -Original Message-
> From: Nord, James [mailto:jn...@nds.com]
> Sent: Wednesday, April 01, 2009 10:08 AM
> To: Maven Users List
> Subject: filtering site resources?
> 
> I have some resources in src/site/resources/to_filter that I 
> want to end up in the project site after filtering.
>  
> I have added the following to the pom but the resources are 
> copies without filtering.
>  
> 
>   
>src/main/filters/filter.propertiess
>   
>   
>
> src/site/resources/to_filter
> true
>
>   
>  
>  
> This didn't work unsuprisingly as site phase doesn't do any 
> filtering...
> so then I tried renaming the files to *.*.vm and added the 
> properties to the pom (using beta6 of the site plugin)
>  
> This also didn't work :-(
>  
> How do I accomplish what I want to do?
>  
> /James
> 
> **
> **
> **
> This e-mail is confidential, the property of NDS Ltd and 
> intended for the addressee only. Any dissemination, copying 
> or distribution of this message or any attachments by anyone 
> other than the intended recipient is strictly prohibited. If 
> you have received this message in error, please immediately 
> notify the postmas...@nds.com and destroy the original 
> message. Messages sent to and from NDS may be monitored. NDS 
> cannot guarantee any message delivery method is secure or error-free.
> Information could be intercepted, corrupted, lost, destroyed, 
> arrive late or incomplete, or contain viruses. We do not 
> accept responsibility for any errors or omissions in this 
> message and/or attachment that arise as a result of 
> transmission. You should carry out your own virus checks 
> before opening any attachment. Any views or opinions 
> presented are solely those of the author and do not 
> necessarily represent those of NDS.
> 
> To protect the environment please do not print this e-mail 
> unless necessary.
> 
> NDS Limited Registered Office: One London Road, Staines, 
> Middlesex, TW18 4EX, United Kingdom. A company registered in 
> England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
> **
> **
> **
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure o

filtering site resources?

[Nord, James]

I have some resources in src/site/resources/to_filter that I want to end
up in the project site after filtering.
 
I have added the following to the pom but the resources are copies
without filtering.
 

  
   src/main/filters/filter.propertiess
  
  
   
src/site/resources/to_filter
true
   
  
 
 
This didn't work unsuprisingly as site phase doesn't do any filtering...
so then I tried renaming the files to *.*.vm and added the properties to
the pom (using beta6 of the site plugin)
 
This also didn't work :-(
 
How do I accomplish what I want to do?
 
/James

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

RE: Release plug-in failing to resolve env vars.

[Nord, James]

I would then have to maintain multiple lists of mirrors for each site
which is error prone.

Currently to add one new repo I only need to add the repo to the profile
(or base pom) and a single entry in the mirror section.




> -Original Message-
> From: Santosh Patel [mailto:santosh@gmail.com] 
> Sent: 17 March 2009 17:09
> To: Maven Users List
> Subject: Re: Release plug-in failing to resolve env vars.
> 
> hi,
> 
> Sorry but could you explain the need for this proxyURL thing. 
> Is this a network proxy?
> why dont you try adding it in the active profile as a 
> property in the settings.xml. I presume it can be done that 
> way, probably.
> 
> Santosh
> 
> On Tue, Mar 17, 2009 at 7:05 PM, Nord, James  wrote:
> 
> > I copied the maven-clean-plugin from a backup local repo 
> and it then 
> > fails resolving the clean-plugins parent.
> >
> > [INFO] Downloading:
> > 
> ${env.proxyURL}/central/org/apache/maven/plugins/maven-plugins/10/mave
> > n-
> > plugins-10.pom
> > [INFO] Downloading:
> > 
> ${env.proxyURL}/central/org/apache/maven/plugins/maven-plugins/10/mave
> > n-
> > plugins-10.pom
> >
> >
> > > -Original Message-
> > > From: Santos Patel [mailto:santos.pa...@tcs.com]
> > > Sent: 17 March 2009 13:01
> > > To: Maven Users List
> > > Subject: RE: Release plug-in failing to resolve env vars.
> > >
> > > hi,
> > >
> > > Can't seem to find out any obvious errors or bugs over here.
> > > Try downloading and installing the maven-clean-plugin 
> manually. Then 
> > > check to see if the same thing pops up for some other plugin.
> > >
> > > add the downloaded plugin using
> > > mvn install:install-file
> > >
> > > Santosh
> > > =-=-=
> > > Notice: The information contained in this e-mail message and/or 
> > > attachments to it may contain confidential or privileged 
> > > information. If you are not the intended recipient, any 
> > > dissemination, use, review, distribution, printing or 
> copying of the 
> > > information contained in this e-mail message and/or 
> attachments to 
> > > it are strictly prohibited. If you have received this 
> communication 
> > > in error, please notify us by reply e-mail or telephone and 
> > > immediately and permanently delete the message and any 
> attachments. 
> > > Thank you
> > >
> > >
> > >
> >
> >
> > 
> **
> >  This e-mail is confidential, the property 
> of NDS Ltd 
> > and intended for the addressee only. Any dissemination, copying or 
> > distribution of this message or any attachments by anyone 
> other than 
> > the intended recipient is strictly prohibited. If you have received 
> > this message in error, please immediately notify the 
> > postmas...@nds.com and destroy the original message. 
> Messages sent to 
> > and from NDS may be monitored. NDS cannot guarantee any message 
> > delivery method is secure or error-free. Information could be 
> > intercepted, corrupted, lost, destroyed, arrive late or 
> incomplete, or contain viruses.
> > We do not accept responsibility for any errors or omissions in this 
> > message and/or attachment that arise as a result of 
> transmission. You 
> > should carry out your own virus checks before opening any 
> attachment. 
> > Any views or opinions presented are solely those of the 
> author and do 
> > not necessarily represent those of NDS.
> >
> > To protect the environment please do not print this e-mail unless 
> > necessary.
> >
> > NDS Limited Registered Office: One London Road, Staines, Middlesex, 
> > TW18 4EX, United Kingdom. A company registered in England and Wales 
> > Registered no. 3080780 VAT no. GB 603 8808 40-00
> >
> > 
> **
> > 
> >
> > 
> -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> 
> --
> Santosh Patel
> 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone oth

RE: Release plug-in failing to resolve env vars.

[Nord, James]

I copied the maven-clean-plugin from a backup local repo and it then
fails resolving the clean-plugins parent.

[INFO] Downloading:
${env.proxyURL}/central/org/apache/maven/plugins/maven-plugins/10/maven-
plugins-10.pom
[INFO] Downloading:
${env.proxyURL}/central/org/apache/maven/plugins/maven-plugins/10/maven-
plugins-10.pom


> -Original Message-
> From: Santos Patel [mailto:santos.pa...@tcs.com] 
> Sent: 17 March 2009 13:01
> To: Maven Users List
> Subject: RE: Release plug-in failing to resolve env vars.
> 
> hi,
> 
> Can't seem to find out any obvious errors or bugs over here. 
> Try downloading and installing the maven-clean-plugin 
> manually. Then check to see if the same thing pops up for 
> some other plugin.
> 
> add the downloaded plugin using
> mvn install:install-file
> 
> Santosh
> =-=-=
> Notice: The information contained in this e-mail message 
> and/or attachments to it may contain confidential or 
> privileged information. If you are not the intended 
> recipient, any dissemination, use, review, distribution, 
> printing or copying of the information contained in this 
> e-mail message and/or attachments to it are strictly 
> prohibited. If you have received this communication in error, 
> please notify us by reply e-mail or telephone and immediately 
> and permanently delete the message and any attachments. Thank you
> 
> 
> 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

RE: Release plug-in failing to resolve env vars.

[Nord, James]

http://jira.codehaus.org/secure/attachment/40724/mvn2.0.10.log
http://jira.codehaus.org/secure/attachment/40727/mvn2.0.10_debug.log
http://jira.codehaus.org/secure/attachment/40725/mvn2.1.0-RC3.log 

> -Original Message-
> From: Martin Höller [mailto:mar...@xss.co.at] 
> Sent: 17 March 2009 11:46
> To: Maven Users List
> Subject: Re: Release plug-in failing to resolve env vars.
> 
> On Tuesday 17 March 2009 Santos Patel wrote:
> > Don't make haste buddy.. It seems you forgot to attach the 
> logs once 
> > again.
> 
> Or the list blocks (large?) attachements? Try pasting it to 
> http://pastebin.com/ or similar an post the link.
> 
> hth,
> - martin
> 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

RE: Release plug-in failing to resolve env vars.

[Nord, James]

Normal logs attached.  Sory I thought these where in the first mail :-(

/James

> -Original Message-
> From: Santos Patel [mailto:santos.pa...@tcs.com] 
> Sent: 17 March 2009 11:25
> To: Maven Users List
> Subject: RE: Release plug-in failing to resolve env vars.
> 
> Can you attach the debug output or the logs...
> 
> Santosh

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

RE: Release plug-in failing to resolve env vars.

[Nord, James]

> Is the proxyURL that you mention a valid URL in the first place...?
> Try this... 
> http://www.ja-sig.org/wiki/display/UPM30/Nexus+Proxy+Example

Yes it is a valid URL.

You can see from the logs that it downloaded everything it needed up
until the forked maven invocation.

/James 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

Release plug-in failing to resolve env vars.

[Nord, James]

Hi all,
 
A while ago I had a problem with my settings containing environment
variables that failed during any forked maven process[1].  This was my
fault as I was referencing ${bob} and not ${env.bob}
I changed this - and all was well in the world for a while - but I
cleaned out my local repostitory and things are failing again.
 
Tested with 2.0.9, 2.0.10, 2.1.0-RC3
 
A simple test project and settings.xml is attached - Am I doing
something incorrect or is this a maven bug?
 
D:\workspaces\svn_all\maven\sandbox\james\buildenvtests\trunk\anothertes
t>set | grep proxyURL
proxyURL=http://nexus/nexus/content/repositories
 
both builds fail as they beleive "env.proxyURL" is undefined - but this
is set as a user variable in windows.
 
/James
 
[1] 
http://mail-archives.apache.org/mod_mbox/maven-users/200901.mbox/%3CFC63
46dcac897f4e9673c4418e6448c80190c...@ukex07.uk.nds.com%3e

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd";>
	
		
			central-mirror
			Maven Central [nexus mirror]
			${env.proxyURL}/central
			central
		
	



http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
	4.0.0
	com.nds.test
	anothertest
	0.0.1-SNAPSHOT
	jar
	Another test project

	
		scm:svn:svn://svnrepo/maven/sandbox/james/buildenvtests/trunk/anothertest 
		scm:svn:svn+ssh://svnrepo/maven/sandbox/james/buildenvtests/trunk/anothertest 
		http://svnrepo/viewvc/sandbox/james/buildenvtests/trunk/anothertest/?root=maven 
	


	
		
			file:///e:/maven/site
		
		
			my-repo
			My Repository
			
file:///e:/maven/repo
			
		
	


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

RE: Maven Multi-module Hierarchy & Archetype

[Nord, James]

http://maven.apache.org/plugins/maven-archetype-plugin/examples/create-m
ulti-module-project.html 

> -Original Message-
> From: jtdeane [mailto:jde...@collaborative.ws] 
> Sent: 16 March 2009 15:16
> To: users@maven.apache.org
> Subject: Maven Multi-module Hierarchy & Archetype
> 
> 
> Is is possible to create a Maven Archetype that would create 
> a Multi-Module Hierarchy? And if it possible could someone 
> please point me to an example or existing documentation?
> --
> View this message in context: 
> http://www.nabble.com/Maven-Multi-module-Hierarchy---Archetype
> -tp22540377p22540377.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

RE: [maven-eclipse-plugin] Define compiler options in POM

[Nord, James]

Can you not change the eclipse worksapce settings instead of the per project 
ones.
Then when the settings get clobbered you will still be using the defaults - but 
the defaults are what you wanted.

/James



> -Original Message-
> From: Daniele Dellafiore [mailto:ilde...@gmail.com] 
> Sent: 04 March 2009 14:19
> To: Maven Users List
> Subject: Re: [maven-eclipse-plugin] Define compiler options in POM
> 
> That is easy, I am talking about all the others:
> 
> org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning
> org.eclipse.jdt.core.compiler.problem.autoboxing=warning
> org.eclipse.jdt.core.compiler.problem.deprecation=warning
> org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedC
> ode=disabled
> 
> and so on...
> 
> On Wed, Mar 4, 2009 at 3:13 PM, Todd Thiessen 
>  wrote:
> > maven-compiler-plugin
> >
> >      
> >        maven-compiler-plugin
> >        
> >          1.5
> >          1.5
> >        
> >      
> >
> > ---
> > Todd Thiessen
> >
> >
> >> -Original Message-
> >> From: Daniele Dellafiore [mailto:ilde...@gmail.com]
> >> Sent: Wednesday, March 04, 2009 9:10 AM
> >> To: Maven Users List
> >> Subject: [maven-eclipse-plugin] Define compiler options in POM
> >>
> >> Hi all.
> >>
> >> Hi have this issue: every time I run mvn eclipse:eclipse the 
> >> .settings folder of the project is cleaned and I lose my project 
> >> specific compiler settings. I would like to keep them or 
> at least be 
> >> able to define them in the POM.
> >>
> >> What solution do you suggest? I have not found any on the web...
> >>
> >> --
> >> Daniele Dellafiore
> >> http://blog.ildella.net/
> >>
> >> 
> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
> > 
> -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> 
> 
> --
> Daniele Dellafiore
> http://blog.ildella.net/
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

RE: Searching for Artifacts in maven

[Nord, James]

Either use a managed proxy like nexus that has this functionality or try
here
http://www.mvnbrowser.com/artifacts-search.html

/James 

> -Original Message-
> From: Vishal Pahwa [mailto:vpa...@sapient.com] 
> Sent: 20 February 2009 10:52
> To: Maven Users List
> Subject: Searching for Artifacts in maven
> 
> 
> Hi
> 
> As we know that in maven we used to address any artifact with 
> the groupId and artifactId.
> 
> Now if I just know which version of a specific artifact I 
> need to use in my project, then what would be the best way to 
> get to know the artifactId and the groupId with which this 
> artifact would be available in any of the Maven mirrors so 
> that I can add this dependency in pom.xml
> 
> 
> Regards
> 
> Vishal
> 
> 

**
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**

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

RE: Release plugin development.

[Nord, James]

Yup that fixed it.

Chnaged the mirror declaration to ${env.proxyURL} and it worked with the 
release plugin.

Strage that it worked at all though and only the release plugin appeared to 
have issues with it.

/James 

> -Original Message-
> From: Deneux, Christophe [mailto:christophe.den...@capgemini.com] 
> Sent: 28 January 2009 13:02
> To: Maven Users List
> Subject: RE : Release plugin development.
> 
> As explain in the settings references, env variable are used 
> with the prefix "env", otherwise it's considered as a 
> property. For example, ${env.PATH} contains the $path 
> environment variable.
>  
> Have you try ? I'm not sure that this will fix your problem, 
> but I'm using the same mirror declaration, but with 
> properties, without problem. A workaround can be to set a new 
> property in your settings.xml instead to use an env variable.
>  
> __
> _
> Christophe DENEUX / Capgemini Sud / Méditerranée Integration 
> Architect / OW2 PEtALS Comitter
> Tel: + 33 4 93 95 55 92 / www.capgemini.com 
> <http://www.capgemini.com/> Porte de l'Arénas - Entrée B / 
> 455 Promenade des Anglais / 06200 Nice / FRANCE Join the 
> Collaborative Business Experience 
> __
> _
> Please consider the environment and do not print this email 
> unless absolutely necessary. Capgemini encourages 
> environmental awareness.
> 
> 
> 
> De: Nord, James [mailto:jn...@nds.com]
> Date: mer. 28/01/2009 13:54
> À: users@maven.apache.org
> Objet : Release plugin development.
> 
> 
> 
> Is the release plugin development ongoing or is this an 
> orphand plugin.
> 
> I ask as I and others have a showstopper with it not 
> inheriting the process environment when doing release:perform.
> http://jira.codehaus.org/browse/MRELEASE-406
> 
> Or does anyone have any bright ideas how to work around this?
> 
> Regards,
> 
> /James
> 
> 
> 
> 
> 
> 
> 
> 
> 
> This message contains information that may be privileged or 
> confidential and is the property of the Capgemini Group. It 
> is intended only for the person to whom it is addressed. If 
> you are not the intended recipient, you are not authorized to 
> read, print, retain, copy, disseminate, distribute, or use 
> this message or any part thereof. If you receive this message 
> in error, please notify the sender immediately and delete all 
> copies of this message.
> 

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

Release plugin development.

[Nord, James]

Is the release plugin development ongoing or is this an orphand plugin.
 
I ask as I and others have a showstopper with it not inheriting the
process environment when doing release:perform.
http://jira.codehaus.org/browse/MRELEASE-406
 
Or does anyone have any bright ideas how to work around this?
 
Regards,
 
/James
 

enforcer and components.

[Nord, James]

Hi all,
 
I have the following in a custom enforcer rule

ScmManager scmManger = (ScmManager)
helper.getComponent(ScmManager.class);

Which fails with "Component descriptor cannot be found in the component
repository: org.apache.maven.scm.manager.ScmManager."

My rule has dependencies on maven-scm-api in it's pom and looking at the
release plugin plexus will resolve the ScmManager.  So how do I get hold
of it inside an enforcer rule?

Regards,

/James


*
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only.  Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited.  If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message.  Messages sent 
to and from NDS may be monitored.  NDS cannot guarantee any message delivery 
method is secure or error-free.  Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.  We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission.  You should carry out your 
own virus checks before opening any attachment.  Any views or opinions 
presented are solely those of the author and do not necessarily represent those 
of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England 
and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**

MailingList inheritance

[Nord, James]

Hi all,
 
I have a parent project that defines all the repositores and plugin
configuration etc which contains a solitary mailing list.
 
Any project that inherits from this also inherits this mailing list and
I can find no way in the child pom of saying there are no mailing lists.
 
If I define a new mailing list then the parents list is removed - but if
I define an empty mailing list section using
 then the parents list is still inherited.  
 
How can I get a sub project to have no mailing lists?
 
/James

*
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only.  Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited.  If you have received this message in error, please immediately 
notify the postmas...@nds.com and destroy the original message.  Messages sent 
to and from NDS may be monitored.  NDS cannot guarantee any message delivery 
method is secure or error-free.  Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.  We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission.  You should carry out your 
own virus checks before opening any attachment.  Any views or opinions 
presented are solely those of the author and do not necessarily represent those 
of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England 
and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**

Checking SCM infromation

[Nord, James]

Hi all,
 
Is there a way to check that the SCM infromation provided in the pom is
correct.
 
example project in svn is http://myserver/repo/trunk/project1/pom.xml
but scm defines connection as
scm:svn:http://someotherserver/trunk/projectx/pom.xml
 
I tried running mvn scm:validate but it just checks the syntax is
correct not that the location is correct.
running scm:diff etc all work as they use the native svn command which
uses the information from the .svn/* files not the information that
maven has.
 
Is there a way to accomplish this (I don't mind if its subversion only
at this point)
 
/James

*
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only.  Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited.  If you have received this message in error, please immediately 
notify the [EMAIL PROTECTED] and destroy the original message.  Messages sent 
to and from NDS may be monitored.  NDS cannot guarantee any message delivery 
method is secure or error-free.  Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.  We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission.  You should carry out your 
own virus checks before opening any attachment.  Any views or opinions 
presented are solely those of the author and do not necessarily represent those 
of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England 
and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**

RE: Maven - build project from SVN

[Nord, James]

Joshi,

Your SCM url is incorrect. 

See http://maven.apache.org/scm/subversion.html

/James

> -Original Message-
> From: Harshal Joshi [mailto:[EMAIL PROTECTED] 
> Sent: 05 December 2008 10:01
> To: Maven Users List
> Cc: [EMAIL PROTECTED]
> Subject: Re: Maven - build project from SVN
> 
> Stephen,
> 
> Thanks man!!! You understand my requirement correctly, I want 
> to checkout files on local and build it locally but it should 
> automatic process, I don't want to manually checkout files.
> 
> I have gone through what you have suggested and check url 
> also and applied scm stuff in pom file.
> 
> my SCM config is below
> 
> scm:svn://ipaddress/trunk/dev
> 
> scm:svn://ipaddress/trunk/dev onnection>
> svn://ipaddress/trunk/dev
> 
>   
> 
>   
> org.apache.maven.plugins
> maven-scm-plugin
> 1.0
> 
>   username
>   password
> 
>   
> 
> 
> 
> but when run mvn scm:bootstrap it throws me error like 
> invalid svn url which is not the case...
> 
> I think I am missing out something so can you pls guide me in 
> tht... I really appreciate your help.
> 
> Thanks,
> HJ
> 
> On Fri, Dec 5, 2008 at 2:10 PM, Stephen Connolly < 
> [EMAIL PROTECTED]> wrote:
> 
> > Hi,
> >
> > AFAIK, there is nothing you can do to avoid the project 
> being checked 
> > out of SVN in order to build it.
> >
> > So ***If I understand your question correctly*** you are 
> looking for a 
> > maven command that will do the checkout for you and then build 
> > locally, do you also want it to tidy up afterwards for you (i.e. 
> > delete the checked out
> > files) leaving the built artifacts in either the local Maven 
> > Repository (if you went for install) or the remote Maven Repository 
> > (if you went for deploy)?
> >
> > The closest I can see for you is:
> >
> > 
> http://maven.apache.org/scm/plugins/examples/bootstrapping-with-pom.ht
> > ml
> >
> > Though that would still require a pom.xml file to tell 
> Maven what to 
> > check-out and build.
> >
> > With regards to being forced to move to ClearCase... I too am 
> > interested in how well the integration with ClearCase works, 
> > especially w.r.t. the release plugin.
> >
> > I can't help wondering if we are working for the same company... 
> > (quickly checks corporate email directory... many Joshis, no 
> > Harshal)... nope, so my employers are not the only people who drank 
> > the ClearCase kool-aid ;-)
> >
> > -Stephen.
> >
> > 2008/12/5 Harshal Joshi <[EMAIL PROTECTED]>
> >
> > > Hi All,
> > >
> > > We are using SVN for repository for many of our projects, earlier 
> > > for
> > build
> > > I use to get latest from SVN and copy it to my local 
> directory and 
> > > from there I use to build it. Now  I want to build 
> directly from SVN 
> > > without copy project to local directory. So can you 
> please suggest 
> > > me how can we build project which are in SVN? Pls also 
> let me know 
> > > you solution will work on ClearCase also or not as we have to 
> > > migrate to ClearCase.
> > >
> > > I would appriecate your efforts.
> > >
> > > Thanks,
> > > HJ
> > >
> >
> 

*
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only.  Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited.  If you have received this message in error, please immediately 
notify the [EMAIL PROTECTED] and destroy the original message.  Messages sent 
to and from NDS may be monitored.  NDS cannot guarantee any message delivery 
method is secure or error-free.  Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.  We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission.  You should carry out your 
own virus checks before opening any attachment.  Any views or opinions 
presented are solely those of the author and do not necessarily represent those 
of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England 
and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**

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

RE: Limitation of the release plugin?

[Nord, James]

> > Todd Thiessen wrote:
> >> The first modification of the pom changes the version to 
> remove the 
> >> "-SNAPSHOT" and also changes the SCM values to point to the tag 
> >> location instead of the trunk location.  Once done, it 
> then commits 
> >> this change to trunk.
> 
> To some extent I think there's a reason for this, which is so 
> that the files will not appear to have been modified on the 
> tag, and the tag is a straight copy of some actual SVN 
> revision, rather than being created out of thin air from a 
> working copy. (Of course, if you branch from a tag and have 
> it increment the branch version numbers, it straight-up 
> modifies the tag and then modifies it back, which bugs me.)
> 
> Something similar is done when branching - version numbers 
> are updated beforehand, then branched, so that the set of 
> revisions on the branch doesn't include the version number 
> change. I guess this is so when you merge over all changes on 
> the branch to the turnk, you don't get a bunch of spurious 
> version number changes that you'd have to ignore.
> 
> >> Can anyone else confirm this? This seems pretty dangerous.
> 
> Certainly confirmable. I guess the main danger is really if 
> someone updates and does a 'mvn deploy' and it blows away 
> your release version. Keeping your release deployment 
> credentials close is good practice, so this would be pretty 
> uncommon in the wild. But it's an issue that maybe bears 
> rethinking nonetheless.

Yes, unfortunaltley it interferes with any(most?) CI systems - as the CI
System has the potential to see the release (on the trunk) and build it.

All my snapshots are built and deployed by the CI system, the only way I
have found to stop this is to disable the project in the CI server
before the release happens - which is a bit labour intensive but better
than changing all the versions and scm location by hand.

/James

*
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only.  Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited.  If you have received this message in error, please immediately 
notify the [EMAIL PROTECTED] and destroy the original message.  Messages sent 
to and from NDS may be monitored.  NDS cannot guarantee any message delivery 
method is secure or error-free.  Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.  We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission.  You should carry out your 
own virus checks before opening any attachment.  Any views or opinions 
presented are solely those of the author and do not necessarily represent those 
of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England 
and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**

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

RE: [deploy-plugin] Abort deploy when a target is present

[Nord, James]

You need a repository manager.
Nexus can do this - others may to.

http://nexus.sonatype.org/about/faq.html#QHowdoIdisableartifactredeploym
ent

/James 

> -Original Message-
> From: solo1970 [mailto:[EMAIL PROTECTED] 
> Sent: 03 December 2008 15:02
> To: users@maven.apache.org
> Subject: Re: [deploy-plugin] Abort deploy when a target is present
> 
> 
> Somehow I'm getting a little bit lost!!!  I tried to read the 
> feeds but I don't quite get it! 
> 
> I'm just starting out with Maven (ver. 2.0.9) and I would 
> like to have this feature of NO re-reployement of the same 
> version.  Can someone summarize? 
> 
> How do I do this?  Is it available 
> 
> Sonia 
> 
> 
> MATHUS Baptiste wrote:
> > 
> > Hi all,
> > 
> > Recently, some developers did a release manually. So they put a 
> > release version in the pom and triggered a deploy. 
> Everything fine but...
> > The thing is: they forgot to re-update the pom.version to a new 
> > snapshot version.
> > 
> > So, as the code is continuously integrated, at each new commit, the 
> > recent release was "automatically" overridden many times with the 
> > snapshot code before realizing it :-/.
> > So, what I would like is to be able to put an additional option for 
> > maven when run inside the continuous integration server, something 
> > like -DdontOverrideRelease, that would make fail the 
> deployment if the 
> > released artefact is already present.
> > 
> > I've taken a quick look at
> > 
> http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html 
> > but it seems it's not currently possible.
> > What do you think? Can a file an feature request about it in the 
> > plugin tracker?
> > 
> > Thanks a lot.
> > 
> > Cheers.
> > --
> > Baptiste
> > 
> > 
> > 
> 
> --
> View this message in context: 
> http://www.nabble.com/-deploy-plugin--Abort-deploy-when-a-targ
> et-is-present-tp16329568p20814596.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]
> 
> 

*
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only.  Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited.  If you have received this message in error, please immediately 
notify the [EMAIL PROTECTED] and destroy the original message.  Messages sent 
to and from NDS may be monitored.  NDS cannot guarantee any message delivery 
method is secure or error-free.  Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.  We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission.  You should carry out your 
own virus checks before opening any attachment.  Any views or opinions 
presented are solely those of the author and do not necessarily represent those 
of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England 
and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**


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

maven version as a property

[Nord, James]

Hi all,
 
I have a need to embed the maven (core) version inside a manifest.  Is
there a property that I can reference inside a pom that is in effect the
Maven (core) version - or do I need to write a plugin to set a property?
 
Regards,
 
/James
 

*
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only.  Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited.  If you have received this message in error, please immediately 
notify the [EMAIL PROTECTED] and destroy the original message.  Messages sent 
to and from NDS may be monitored.  NDS cannot guarantee any message delivery 
method is secure or error-free.  Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.  We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission.  You should carry out your 
own virus checks before opening any attachment.  Any views or opinions 
presented are solely those of the author and do not necessarily represent those 
of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England 
and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**

plain old application packaging

[Nord, James]

Hi all,
 
I have maven building several projects some of which are common and some
are shared between applications.  
 
I want to be able to have a build that contains specific project
dependencies and produces a bundled result - such as a zip that can be
taken and given to the packaging/installation team.  As I'm not using
web technology I can't find a packaging type that's suitable - but I
would have thought this is a fairly generic requirement.
 
Have I missed something obvious in Google - or could someone give me a
suggestion.
 
Regards,
 
/James
*
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only.  Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited.  If you have received this message in error, please immediately 
notify the [EMAIL PROTECTED] and destroy the original message.  Messages sent 
to and from NDS may be monitored.  NDS cannot guarantee any message delivery 
method is secure or error-free.  Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.  We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission.  You should carry out your 
own virus checks before opening any attachment.  Any views or opinions 
presented are solely those of the author and do not necessarily represent those 
of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West 
Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England 
and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**