Re: Including dependencies in a jar
There is also the Application Assembler Maven Plugin:
http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/
/Anders
On Thu, Mar 10, 2011 at 03:03, Benson Margulies wrote:
> maven-shade-plugin, or just use the assembly plugin to colocate the
> dependencies and ask the jar plugin to add a manifest to the main jar.
>
> On Wed, Mar 9, 2011 at 8:53 PM, Mark wrote:
> > Say I have the following dependency:
> >
> >
> > org.apache.mahout.commons
> > commons-cli
> > 2.0-mahout
> >
> >
> > And my main class makes use of these classes:
> >
> > public static void main(String[] args) throws Exception {
> > DefaultOptionBuilder optionBuilder = new DefaultOptionBuilder();
> >
> > }
> >
> > Now when I compile my jar everything is ok however when I try to run my
> > application I get a ClassNotFound exception. How can I jar up my code
> with
> > the required dependencies and add its classpath?
> >
> > Thanks alot.
> >
> >
> >
> > -
> > 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: Bad mojo. Builds under maven2, fails under maven3.
While I don't have time to dig into this, I'm offering a (well founded) guess as you're mentioning maven-antrun-plugin. In Maven 2, all executions of a plugin (maven-antrun-plugin for example) within a build share the same classpath. So the first execution sets the classpath, and regardless on how you specify it in the other executions the get the first execution's classpath. This is a limitation/bug in Maven 2, that has been fixed in Maven 3. So in Maven 3, every execution gets it's own classpath based on the pom. I think this is why you're getting different dependencies (plugin classpath). And the reason for the build not to work is that the dependencies (plugin classpath) is incorrect. You need to fix that in the pom. This issue with Maven 2 often caused problems with maven-antrun-plugin as some people use it a lot within a multi-module build. There's some more info on this in reason #7 on my blog post on why to move to Maven 3 [1]. /Anders [1] http://www.sonatype.com/people/2011/02/top-ten-reasons-to-move-to-maven-3/ On Thu, Mar 10, 2011 at 03:01, wrote: > I've almost succeeded in getting all of my developer end-user's projects > building under maven3 (3.0.3). This one project builds fine under maven2 > (2.2.1) but fails under maven3. I'm not a programmer, just a SysAdmin, but > from looking at the debug output of a successful run and a failed one, it > seems like maven3 is not coming up with the same dependency list as maven2 > and thus the mojo (I have *no* idea what that means, in this context, heh) > for maven-antrun-plugin 1.3 comes out wrong and the build fails. > > Excerpt from the maven2 build: > > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-antrun-plugin:1.3:run' --> > [DEBUG] (f) pluginArtifacts = > [org.apache.ant:ant-nodeps:jar:1.7.0:compile, > org.apache.ant:ant:jar:1.7.1:runtime, > org.apache.ant:ant-launcher:jar:1.7.1:runtime, > ant-contrib:ant-contrib:jar:1.0b3:compile, ant:ant:jar:1.5:compile, > org.codehaus.plexus:plexus-utils:jar:1.5.6:runtime, > org.apache.maven:maven-plugin-api:jar:2.0.4:runtime, > org.apache.maven:maven-project:jar:2.0.4:runtime, > org.apache.maven:maven-artifact:jar:2.0.4:runtime] > > Excerpt from the maven3 build: > > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-antrun-plugin:1.3:run' with override > configurator --> > [DEBUG] (f) pluginArtifacts = > [org.apache.maven.plugins:maven-antrun-plugin:maven-plugin:1.3:, > org.apache.ant:ant-nodeps:jar:1.7.0:runtime, > ant-contrib:ant-contrib:jar:1.0b3:runtime, ant:ant:jar:1.5:runtime, > junit:junit:jar:3.8.1:compile, > org.codehaus.plexus:plexus-utils:jar:1.5.6:compile, > org.apache.ant:ant-launcher:jar:1.7.1:runtime, > org.apache.ant:ant:jar:1.7.1:compile] > > There are several differences. The maven3 build lacks maven-plugin-api, > maven-project and maven-artifact, but adds junit. For all the jars they have > in common, with the exception of ant-launcher, maven3 flipped what maven2 > had selected for compile and runtime, to runtime and compile, respectively. > Maven3 seems to be quite contrary! :) > > The rest of this long email is the sections from both debug logs that show > how they arrived at the above. I'm hoping one of you can tell me how to get > maven3 to do the right thing, so I can get past this build error. Thank you > SO MUCH for taking the time to pour over it and for any assistance you might > offer. :) > > > From the maven2 build: > == > > ... > [DEBUG] Plugin dependencies for: > > org.apache.maven.plugins:maven-antrun-plugin:1.3 > > are: > > org.apache.ant:ant-nodeps:jar:1.7.0:compile > ant-contrib:ant-contrib:jar:1.0b3:compile > org.apache.maven:maven-plugin-api:jar:2.0.4:runtime > org.apache.maven:maven-project:jar:2.0.4:runtime > org.apache.maven:maven-artifact:jar:2.0.4:runtime > org.codehaus.plexus:plexus-utils:jar:1.5.6:runtime > org.apache.ant:ant-launcher:jar:1.7.1:runtime > org.apache.ant:ant:jar:1.7.1:runtime > > > [DEBUG] > org.apache.maven.plugins:maven-antrun-plugin:maven-plugin:1.3:runtime > (selected for runtime) > [DEBUG] Retrieving parent-POM: org.apache.ant:ant-parent:pom:1.7.0 for > project: org.apache.ant:ant-nodeps:jar:1.7.0 from the repository. > [DEBUG] org.apache.ant:ant-nodeps:jar:1.7.0:compile (selected for > compile) > [DEBUG] org.apache.ant:ant:jar:1.7.0:compile (selected for compile) > [DEBUG] org.apache.ant:ant-launcher:jar:1.7.0:compile (selected for > compile) > [DEBUG] ant-contrib:ant-contrib:jar:1.0b3:compile (selected for compile) > [DEBUG] ant:ant:jar:1.5:compile (selected for compile) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven:pom:2.0.4 for > project: org.apache.maven:maven-plugin-api:jar:2.0.4 from the repository. > [DEBUG] Adding managed dependencies for org.apache.maven:maven-plugin-api > [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1 > [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-a
Re: AuthChallengeProcessor selectAuthScheme [more info]
> Mar 9, 2011 3:47:41 PM > org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme > INFO: basic authentication scheme selected I haven't looked into this myself, but the messages sure seem like they are being generated by o.a.c.httpclient (or the webdav wagon) and not Maven itself. So you may want to talk to the Apache Commons folks about it but you may want to look into it a little bit more yourself first to confirm before reporting an actual issue. This may be a known bug where some logging is being piped to stderr rather than to the console and it has been fixed in a more recent release, or its something new that they should track and fix. Or, as you've mentioned, it may be due to an interaction with the webdav wagon, hard to know without spending a bit of time looking into it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Including dependencies in a jar
On Thu, Mar 10, 2011 at 04:50, Mark wrote:
> Can you please explain the assembly plugin method?
Take a look at:
http://thomassundberg.wordpress.com/2011/03/05/create-an-executable-jar-from-maven/
/Thomas
>
> Thanks
>
> On 3/9/11 6:03 PM, Benson Margulies wrote:
>>
>> maven-shade-plugin, or just use the assembly plugin to colocate the
>> dependencies and ask the jar plugin to add a manifest to the main jar.
>>
>> On Wed, Mar 9, 2011 at 8:53 PM, Mark wrote:
>>>
>>> Say I have the following dependency:
>>>
>>>
>>> org.apache.mahout.commons
>>> commons-cli
>>> 2.0-mahout
>>>
>>>
>>> And my main class makes use of these classes:
>>>
>>> public static void main(String[] args) throws Exception {
>>> DefaultOptionBuilder optionBuilder = new DefaultOptionBuilder();
>>>
>>> }
>>>
>>> Now when I compile my jar everything is ok however when I try to run my
>>> application I get a ClassNotFound exception. How can I jar up my code
>>> with
>>> the required dependencies and add its classpath?
>>>
>>> Thanks alot.
>>>
>>>
>>>
>>> -
>>> 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
>
>
--
Thomas Sundberg
M. Sc. in Computer Science
Mobile: +46 70 767 33 15
Blog: http://thomassundberg.wordpress.com/
Twitter: @thomassundberg
Better software through faster feedback
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Including dependencies in a jar
Can you please explain the assembly plugin method?
Thanks
On 3/9/11 6:03 PM, Benson Margulies wrote:
maven-shade-plugin, or just use the assembly plugin to colocate the
dependencies and ask the jar plugin to add a manifest to the main jar.
On Wed, Mar 9, 2011 at 8:53 PM, Mark wrote:
Say I have the following dependency:
org.apache.mahout.commons
commons-cli
2.0-mahout
And my main class makes use of these classes:
public static void main(String[] args) throws Exception {
DefaultOptionBuilder optionBuilder = new DefaultOptionBuilder();
}
Now when I compile my jar everything is ok however when I try to run my
application I get a ClassNotFound exception. How can I jar up my code with
the required dependencies and add its classpath?
Thanks alot.
-
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: Including dependencies in a jar
maven-shade-plugin, or just use the assembly plugin to colocate the
dependencies and ask the jar plugin to add a manifest to the main jar.
On Wed, Mar 9, 2011 at 8:53 PM, Mark wrote:
> Say I have the following dependency:
>
>
> org.apache.mahout.commons
> commons-cli
> 2.0-mahout
>
>
> And my main class makes use of these classes:
>
> public static void main(String[] args) throws Exception {
> DefaultOptionBuilder optionBuilder = new DefaultOptionBuilder();
>
> }
>
> Now when I compile my jar everything is ok however when I try to run my
> application I get a ClassNotFound exception. How can I jar up my code with
> the required dependencies and add its classpath?
>
> Thanks alot.
>
>
>
> -
> 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
Bad mojo. Builds under maven2, fails under maven3.
I've almost succeeded in getting all of my developer end-user's projects building under maven3 (3.0.3). This one project builds fine under maven2 (2.2.1) but fails under maven3. I'm not a programmer, just a SysAdmin, but from looking at the debug output of a successful run and a failed one, it seems like maven3 is not coming up with the same dependency list as maven2 and thus the mojo (I have *no* idea what that means, in this context, heh) for maven-antrun-plugin 1.3 comes out wrong and the build fails. Excerpt from the maven2 build: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.3:run' --> [DEBUG] (f) pluginArtifacts = [org.apache.ant:ant-nodeps:jar:1.7.0:compile, org.apache.ant:ant:jar:1.7.1:runtime, org.apache.ant:ant-launcher:jar:1.7.1:runtime, ant-contrib:ant-contrib:jar:1.0b3:compile, ant:ant:jar:1.5:compile, org.codehaus.plexus:plexus-utils:jar:1.5.6:runtime, org.apache.maven:maven-plugin-api:jar:2.0.4:runtime, org.apache.maven:maven-project:jar:2.0.4:runtime, org.apache.maven:maven-artifact:jar:2.0.4:runtime] Excerpt from the maven3 build: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.3:run' with override configurator --> [DEBUG] (f) pluginArtifacts = [org.apache.maven.plugins:maven-antrun-plugin:maven-plugin:1.3:, org.apache.ant:ant-nodeps:jar:1.7.0:runtime, ant-contrib:ant-contrib:jar:1.0b3:runtime, ant:ant:jar:1.5:runtime, junit:junit:jar:3.8.1:compile, org.codehaus.plexus:plexus-utils:jar:1.5.6:compile, org.apache.ant:ant-launcher:jar:1.7.1:runtime, org.apache.ant:ant:jar:1.7.1:compile] There are several differences. The maven3 build lacks maven-plugin-api, maven-project and maven-artifact, but adds junit. For all the jars they have in common, with the exception of ant-launcher, maven3 flipped what maven2 had selected for compile and runtime, to runtime and compile, respectively. Maven3 seems to be quite contrary! :) The rest of this long email is the sections from both debug logs that show how they arrived at the above. I'm hoping one of you can tell me how to get maven3 to do the right thing, so I can get past this build error. Thank you SO MUCH for taking the time to pour over it and for any assistance you might offer. :) >From the maven2 build: == ... [DEBUG] Plugin dependencies for: org.apache.maven.plugins:maven-antrun-plugin:1.3 are: org.apache.ant:ant-nodeps:jar:1.7.0:compile ant-contrib:ant-contrib:jar:1.0b3:compile org.apache.maven:maven-plugin-api:jar:2.0.4:runtime org.apache.maven:maven-project:jar:2.0.4:runtime org.apache.maven:maven-artifact:jar:2.0.4:runtime org.codehaus.plexus:plexus-utils:jar:1.5.6:runtime org.apache.ant:ant-launcher:jar:1.7.1:runtime org.apache.ant:ant:jar:1.7.1:runtime [DEBUG] org.apache.maven.plugins:maven-antrun-plugin:maven-plugin:1.3:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.ant:ant-parent:pom:1.7.0 for project: org.apache.ant:ant-nodeps:jar:1.7.0 from the repository. [DEBUG] org.apache.ant:ant-nodeps:jar:1.7.0:compile (selected for compile) [DEBUG] org.apache.ant:ant:jar:1.7.0:compile (selected for compile) [DEBUG] org.apache.ant:ant-launcher:jar:1.7.0:compile (selected for compile) [DEBUG] ant-contrib:ant-contrib:jar:1.0b3:compile (selected for compile) [DEBUG] ant:ant:jar:1.5:compile (selected for compile) [DEBUG] Retrieving parent-POM: org.apache.maven:maven:pom:2.0.4 for project: org.apache.maven:maven-plugin-api:jar:2.0.4 from the repository. [DEBUG] Adding managed dependencies for org.apache.maven:maven-plugin-api [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-ssh-external:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-6 [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.4:runtime (selected for runtime) [DEBUG] Adding managed dependencies for unknown:maven-project [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-ssh-external:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-6 [DEBUG] org.apache.maven:maven-project:jar:2.0.4:runtime (selected for runtime) [DEBUG] Adding managed dependencies for unknown:maven-settings [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 [DEBUG]
Including dependencies in a jar
Say I have the following dependency:
org.apache.mahout.commons
commons-cli
2.0-mahout
And my main class makes use of these classes:
public static void main(String[] args) throws Exception {
DefaultOptionBuilder optionBuilder = new DefaultOptionBuilder();
}
Now when I compile my jar everything is ok however when I try to run my
application I get a ClassNotFound exception. How can I jar up my code
with the required dependencies and add its classpath?
Thanks alot.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: AuthChallengeProcessor selectAuthScheme [more info]
It seems that these messages, which I started getting tons of after our maven2 to maven3 switch: Mar 9, 2011 3:47:41 PM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected are directly related to our use of the webdav wagon. I added the wagon as a build extension to our project, as it was using webdav but that wagon isn't included in Maven3 by default. When I instead simply made it a dependency of maven-deploy-pugin, so it was only used for deploying, the number of messages went down. I then changed our pom.xml files to not use webdav at all and now the messages have gone away entirely. What is the benefit to using webdav over plain http? Am I losing something important by not using it? If I'm to use webdav, then is there something I need to configure to prevent it from spewing these lines to STDERR, and causing our build wrapper scripts to fail, even though the build succeeds? These weren't an issue with Maven2 ... Thanks, in advance, for you time and assistance. -ste This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Deploying via SSH on Windows
I'm trying to setup deployment via SSH on Windows, but keep running into the
following problem:[INFO] [deploy:deploy {execution: default-deploy}][DEBUG] not
adding permissions to wagon connectionUploading:
scpexe://myrepo.com/path/to/repository/com/ptc/jenkins/ptc-logparser/1.001/ptc-logparser-1.001.hpi[DEBUG]
Executing command: mkdir -p
/path/to/repository/com/ptc/jenkins/ptc-logparser/1.001
[DEBUG] Exit code 255 - Host key verification failed.
org.apache.maven.wagon.CommandExecutionException: Exit code 255 - Host key
verification failed.
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand(ScpExternalWagon.java:209)
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand(ScpExternalWagon.java:149)
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:389)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317)
My POM has:
ptc-plugin-repoPTC Jenkins Plugin Repository
scpexe://myrepo.com/path/to/repository
My settings.xml has:ptc-plugin-repo
jenkinsupdate
All of my searching for a solution keeps pointing me to articles suggesting
that I setup public key authentication, but I've already done that. It works
fine from a command prompt (ssh jenkinsupd...@myrepo.com logs me in without
prompting me for a password). It is only from within Maven that is seems to
fail authentication. I dual boot Windows and Ubuntu and I'm using the same
settings.xml and SSH key in both. Deploying works in Ubuntu, but not in
Windows.
The SSH client I'm using on Windows is the one packaged with
msysgit:OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
I've also tried using OpenSSH for Windows as a separate
install:OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004
My Maven version:Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500)Java
version: 1.6.0_23Java home: D:\devtools\JavaJDK_1.6\jreDefault locale: en_US,
platform encoding: Cp1252OS name: "windows xp" version: "5.1" arch: "x86"
Family: "windows"
Any ideas?
Mike
Re: repository sharing
shaun.t.erick...@accenture.com wrote: > Can maven 2.2.1 & maven 3.0.3 share the same .m2 directory and > settings.xml file, without any problems? It looks like I will need to > support the use of both for some time and it would be nice if I didn't > have to have a .m2 and settings.xml for each. Yes. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: getRuntimeArtifacts and provided scope
Hi Mathieu, Mathieu wrote: > Hi, > > we are trying to implement a maven Mojo. In the Mojo we call the > getRuntimeArtifacts method > on the maven project object in order to list all the dependencies which > need to be present > at runtime. The problem is that we don't get any "provided scope" > dependency whereas one is defined > in the pom.xml on the builded project (in the result of > getRuntimeArtifacts the provided dependency > does not show up). > > Any idea on that? This is exactly, what provided means: It's provided by the runtime platform, your application can expect those artifacts (resp. the classes of those artifacts) to be present without having to deliver them. E.g. it does make sense to set javax.activation:activation to "provided", because it is nowaday part of the Java runtime. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: repository sharing
I'm sure it can or cannot be done but I do know we avoid that and maintain one local per version of Maven we support on each build agent. Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day > -Original Message- > From: shaun.t.erick...@accenture.com > [mailto:shaun.t.erick...@accenture.com] > Sent: Wednesday, March 09, 2011 2:25 PM > To: users@maven.apache.org > Subject: repository sharing > > Can maven 2.2.1 & maven 3.0.3 share the same .m2 directory > and settings.xml file, without any problems? It looks like I > will need to support the use of both for some time and it > would be nice if I didn't have to have a .m2 and settings.xml > for each. > > -ste > > > This message is for the designated recipient only and may > contain privileged, proprietary, or otherwise private > information. If you have received it in error, please notify > the sender immediately and delete the original. Any other use > of the email by you is prohibited. > This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AuthChallengeProcessor selectAuthScheme
(My apologies for reposting this. I accidentally sent it out without a subject, yesterday, and suspect no one noticed it as a result.) I'm a SysAdmin trying to help my developer end-users switch from maven2 to maven3. Their build is producing many of these (over a thousand): Mar 8, 2011 6:12:29 PM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected They are being written to STDERR, which is causing our build wrapper scripts to fail, though the build appears to otherwise succeed, but for these. Needless to say, we don't get these messages when using maven2 (I just checked one of our production builds, to be sure). I'm not sure where to begin, with this one. I googled a bit and messages like this seemed to be mentioned in relation to various coding errors people had made. But, for us, this is strictly a maven2 vs. maven3 issue. The code didn't change. Suggestions? Thank you, in advance for your time and assistance. Additionally, thanks for the help I've gotten here so far! :) -ste This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
repository sharing
Can maven 2.2.1 & maven 3.0.3 share the same .m2 directory and settings.xml file, without any problems? It looks like I will need to support the use of both for some time and it would be nice if I didn't have to have a .m2 and settings.xml for each. -ste This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Versioning sub-modules as well as the project as a whole.
have a look at some of the goals in versions-maven-plugin [yoda], might able be to help you they might[/yoda] On 9 March 2011 18:16, Daryl Lonnon wrote: > Joachim, > > So effectively, each of the modules you wish to version separately, is > treated as it's own release. Then you have a separate release (the dep > module) that specifies dependency to all of your other modules. > > Do each of your "sub" modules (the non dependency module) keep track of > their own versioning and dependencies? > > "mvn release" will handle tracking of the version of the module but not > it's > dependencies (IIRC). How do you update those dependency versions before and > after a release (do you do it by hand)? > > Do each of these modules have a common parent pom.xml (and do you track > dependencies in that)? > > Right now, I'm thinking of writing a script that does a release, since I'm > not seeing an easy way to do it within the maven framework. But I'd love to > be shown how to make it work within that framework cleanly. > > Daryl > > > On Wed, Mar 9, 2011 at 6:00 AM, Joachim Van der Auwera >wrote: > > > The way we handle this in the Geomajas project is for (sets of) modules > to > > have their own version and have one module (the -dep module) which only > > contains a pom with dependencyManagement section which defines the latest > > version of all modules (actually this pulls in the parent module for each > > set of modules to assure all dependency versions contained in the > > dependencyManagement of these modules are pulled in). > > > > Hoping my explanation is somewhat understandable. > > > > Kind regards, > > Joachim > > > > > > On 03/09/2011 12:47 AM, Daryl Lonnon wrote: > > > >> Hi, hopefully someone can help me with this. > >> > >> So I have a situation where I have a project with multiple sub-projects. > >> Some of the sub-projects depend on one another. > >> > >> I'd like to version the sub-projects independently while still releasing > >> something that defines the project as a whole. Some of the sub-projects > >> have > >> associated resources files that can be quite large, so ideally you > >> wouldn't > >> have to re-release them if they haven't changed. Also it'd be nice if > >> after > >> a release, the development environment reverts back to the next versions > >> SNAPSHOTs. > >> > >> So my wish list looks like: > >> 1. I'd like to version the sub projects independently. > >> 2. I'd like to be able to release a "global" version which defines the > set > >> of sub-projects that work with one another. > >> 3. I'd like to not release sub-projects that haven't changed just to > >> release > >> a "global" version. > >> 4. I'd like to have my development environment be cohesive after a > release > >> (i.e. point to my local repositiories SNAPSHOTS for the sub-project > >> inter-dependencies).. > >> > >> Has anyone ever tried to do something like this? > >> > >> I've found: > >> > >> > http://out-println.blogspot.com/2008/10/maven-modules-with-independent-versions.html > >> but that scheme doesn't support wish 4 as far as I can tell. > >> > >> Daryl > >> > >> > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
getRuntimeArtifacts and provided scope
Hi, we are trying to implement a maven Mojo. In the Mojo we call the getRuntimeArtifacts method on the maven project object in order to list all the dependencies which need to be present at runtime. The problem is that we don't get any "provided scope" dependency whereas one is defined in the pom.xml on the builded project (in the result of getRuntimeArtifacts the provided dependency does not show up). Any idea on that? Mathieu
Re: Versioning sub-modules as well as the project as a whole.
Joachim, So effectively, each of the modules you wish to version separately, is treated as it's own release. Then you have a separate release (the dep module) that specifies dependency to all of your other modules. Do each of your "sub" modules (the non dependency module) keep track of their own versioning and dependencies? "mvn release" will handle tracking of the version of the module but not it's dependencies (IIRC). How do you update those dependency versions before and after a release (do you do it by hand)? Do each of these modules have a common parent pom.xml (and do you track dependencies in that)? Right now, I'm thinking of writing a script that does a release, since I'm not seeing an easy way to do it within the maven framework. But I'd love to be shown how to make it work within that framework cleanly. Daryl On Wed, Mar 9, 2011 at 6:00 AM, Joachim Van der Auwera wrote: > The way we handle this in the Geomajas project is for (sets of) modules to > have their own version and have one module (the -dep module) which only > contains a pom with dependencyManagement section which defines the latest > version of all modules (actually this pulls in the parent module for each > set of modules to assure all dependency versions contained in the > dependencyManagement of these modules are pulled in). > > Hoping my explanation is somewhat understandable. > > Kind regards, > Joachim > > > On 03/09/2011 12:47 AM, Daryl Lonnon wrote: > >> Hi, hopefully someone can help me with this. >> >> So I have a situation where I have a project with multiple sub-projects. >> Some of the sub-projects depend on one another. >> >> I'd like to version the sub-projects independently while still releasing >> something that defines the project as a whole. Some of the sub-projects >> have >> associated resources files that can be quite large, so ideally you >> wouldn't >> have to re-release them if they haven't changed. Also it'd be nice if >> after >> a release, the development environment reverts back to the next versions >> SNAPSHOTs. >> >> So my wish list looks like: >> 1. I'd like to version the sub projects independently. >> 2. I'd like to be able to release a "global" version which defines the set >> of sub-projects that work with one another. >> 3. I'd like to not release sub-projects that haven't changed just to >> release >> a "global" version. >> 4. I'd like to have my development environment be cohesive after a release >> (i.e. point to my local repositiories SNAPSHOTS for the sub-project >> inter-dependencies).. >> >> Has anyone ever tried to do something like this? >> >> I've found: >> >> http://out-println.blogspot.com/2008/10/maven-modules-with-independent-versions.html >> but that scheme doesn't support wish 4 as far as I can tell. >> >> Daryl >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Updating a properties file using Maven and project classpath information
On 09/03/2011 11:52 AM, Wayne Fay wrote: As discussed there [1], the main issue is that Netbeans can either recognize the project as a Maven one or a JavaFX one but not both. In one case, you lose the JavaFXScript syntax helper from Netbeans JavaFX module, and on the other case you lose Maven dependency resolution. Maybe try on their forum (NetBeans or JavaFX) if they have one. This does sound like something that others would have run into. Ron Sounds like a defect in Netbeans. I would talk to them about getting it fixed. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Updating a properties file using Maven and project classpath information
> As discussed there [1], the main issue is that Netbeans can either recognize > the project as a Maven one or a JavaFX one but not both. In one case, you > lose the JavaFXScript syntax helper from Netbeans JavaFX module, and on the > other case you lose Maven dependency resolution. Sounds like a defect in Netbeans. I would talk to them about getting it fixed. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
make surefire show full stacktrace in plain reports
Hello, What can i do to make surefire show full stacktrace in console and plain txt reports under surefire reports ? when i use the option *redirectTestOutputToFile* I have the trace but not the error stacktrace*.* Help please :) Here's my plugin configuration : On Wed, Mar 9, 2011 at 5:16 PM, Wendy Smoak wrote: > On Wed, Mar 9, 2011 at 9:22 AM, Jochen Wiedmann > wrote: > > No chance? > > I would probably package the site up as a zip and put it in the > repository, then dependency:unpack it where you want it in the webapp. > That assumes the documentation is in a separate module. > > Otherwise, I'd probably just expect to run "mvn site install" in order > to build it (not trying to bind an execution of the site plugin in the > project pom, as you've noted it has side effects.) > > If that doesn't help, try posting a simple example project that > demonstrates the problem so people can play with it. > > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: How to include site into war file?
On Wed, Mar 9, 2011 at 9:22 AM, Jochen Wiedmann wrote: > No chance? I would probably package the site up as a zip and put it in the repository, then dependency:unpack it where you want it in the webapp. That assumes the documentation is in a separate module. Otherwise, I'd probably just expect to run "mvn site install" in order to build it (not trying to bind an execution of the site plugin in the project pom, as you've noted it has side effects.) If that doesn't help, try posting a simple example project that demonstrates the problem so people can play with it. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Updating a properties file using Maven and project classpath information
Le 09/03/2011 15:45, Ron Wheeler wrote : It is always a good idea to describe the problem that you are trying to solve before asking a detailed question. I'm trying to make JavaFX, Maven and Netbeans interact nicely in a multi-modules project (i.e. project is built using Maven but code completion must work fine in Netbeans). The project structure is: myproject + pom.xml (root POM) + core (pure Java module) + pom.xml + fxclient(Java/JavaFX module; depends on: core) + pom.xml As discussed there [1], the main issue is that Netbeans can either recognize the project as a Maven one or a JavaFX one but not both. In one case, you lose the JavaFXScript syntax helper from Netbeans JavaFX module, and on the other case you lose Maven dependency resolution. One way to solve this issue is to update the project.properties with the list of JARs built from the POM using 'maven-ant-tasks' [2]. However, this work-around does not work when the JavaFX project is a module within a multi-modules project (since the Ant task is targetting the pom of the JavaFX module, not the root pom). So I was trying to find another way of having the project.properties updated automatically from Maven. Has someone encountered the same problem ? [1] http://groups.google.com/group/javaposse/browse_thread/thread/f862b782de787bfd [2] http://www.intermedia.uio.no/pages/viewpage.action?pageId=43516820 Le 09/03/2011 15:45, Ron Wheeler wrote : That sounds like a bad idea. The next person to work on the project is going to be unhappy. Why do you want to do this? It is always a good idea to describe the problem that you are trying to solve before asking a detailed question. What are you building that is different from everything else. Ron On 09/03/2011 8:42 AM, Benoît DEL BASSO wrote: Hello, I'm trying to update a properties file using classpath information from a POM file. For example my POM defines a dependency: commons-lang commons-lang 2.4 I would like to update the "private.properties" file (Netbeans) so that it has: maven.dependency.classpath=/home/bdelbass/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar Does somebody has an idea on how to do that? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Benoît Del Basso benoit.delba...@helmet.fr Tél: 01 75 43 43 42 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Integrate Maven Plugin Code (Mojo's) into Application
Hi Karl, FYI, TestNG's pom.xml stopped depending on Guice 2.0 recently, please make sure you're depending on TestNG's latest version (5.14.10). -- Cédric On Wed, Mar 9, 2011 at 4:25 AM, Karl Heinz Marbaise wrote: > Hi Stuart, > > first thanks for your answer > > > Stuart McCulloch wrote: > > > > Looks like a known Surefire bug when using TestNG - recent releases of > > TestNG include Guice 2 as a dependency and it leaks onto the test > > classpath. > > Guice 2 doesn't have JSR330 support, hence the error (it only looks for > > Guice's BindingAnnotation, and doesn't see the javax.inject.Qualifier > > annotation) > > > > Solution is to use this configuration for now: > > > > > > maven-surefire-plugin > > 2.7.2 > > > > false > > > > > > > > I have tried that...may be i missed to mention that my tests where it > failed > are integration tests (via maven-failsafe-plugin) but tried the > configuration there as well and the result was sadly the same ...it doesn't > work. > > However ...may be the reason for not working is that my application uses > guice 2.0 as well.. > > Kind regards > Karl Heinz Marbaise > > > - > Kind regards > Karl Heinz Marbaise > > http://www.soebes.de > http://www.skmwiki.de > http://supose.org/wiki/supose > -- > View this message in context: > http://maven.40175.n5.nabble.com/Integrate-Maven-Plugin-Code-Mojo-s-into-Application-tp3397120p3415401.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 > > -- Cédric
Re: Updating a properties file using Maven and project classpath information
That sounds like a bad idea. The next person to work on the project is going to be unhappy. Why do you want to do this? It is always a good idea to describe the problem that you are trying to solve before asking a detailed question. What are you building that is different from everything else. Ron On 09/03/2011 8:42 AM, Benoît DEL BASSO wrote: Hello, I'm trying to update a properties file using classpath information from a POM file. For example my POM defines a dependency: commons-lang commons-lang 2.4 I would like to update the "private.properties" file (Netbeans) so that it has: maven.dependency.classpath=/home/bdelbass/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar Does somebody has an idea on how to do that? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Updating a properties file using Maven and project classpath information
> I would like to update the "private.properties" file (Netbeans) so that it > has: > maven.dependency.classpath=/home/bdelbass/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar I don't know this file, but you seem to suggest it is a Netbeans-specific file? If so, there may be an option to do this in the nbm-maven-plugin. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to include site into war file?
No chance?
On Fri, Mar 4, 2011 at 1:53 PM, Jochen Wiedmann
wrote:
> Hi,
>
> I've got a project, which is distributed as a web application. I'd
> like to include the site into the webapp. As you possibly know, the
> assembly plugin does support this, so it shouldn't be all too
> impossible.
>
> I tried the following snippet in my POM. Unfortunately, this seems to
> trigger an endless loop between the site and the javadoc plugin.
>
> Any other ideas how I might achieve my goal?
>
> Thanks,
>
> Jochen
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-site-plugin
>
>
> generate-resources
>
> site
>
>
> ${webappDirectory}/docs
>
>
>
>
>
>
>
>
> --
> I Am What I Am And That's All What I Yam (Popeye)
>
--
I Am What I Am And That's All What I Yam (Popeye)
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Updating a properties file using Maven and project classpath information
Hello, I'm trying to update a properties file using classpath information from a POM file. For example my POM defines a dependency: commons-lang commons-lang 2.4 I would like to update the "private.properties" file (Netbeans) so that it has: maven.dependency.classpath=/home/bdelbass/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar Does somebody has an idea on how to do that? -- Benoît Del Basso benoit.delba...@helmet.fr Tél: 01 75 43 43 42 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Versioning sub-modules as well as the project as a whole.
The way we handle this in the Geomajas project is for (sets of) modules to have their own version and have one module (the -dep module) which only contains a pom with dependencyManagement section which defines the latest version of all modules (actually this pulls in the parent module for each set of modules to assure all dependency versions contained in the dependencyManagement of these modules are pulled in). Hoping my explanation is somewhat understandable. Kind regards, Joachim On 03/09/2011 12:47 AM, Daryl Lonnon wrote: Hi, hopefully someone can help me with this. So I have a situation where I have a project with multiple sub-projects. Some of the sub-projects depend on one another. I'd like to version the sub-projects independently while still releasing something that defines the project as a whole. Some of the sub-projects have associated resources files that can be quite large, so ideally you wouldn't have to re-release them if they haven't changed. Also it'd be nice if after a release, the development environment reverts back to the next versions SNAPSHOTs. So my wish list looks like: 1. I'd like to version the sub projects independently. 2. I'd like to be able to release a "global" version which defines the set of sub-projects that work with one another. 3. I'd like to not release sub-projects that haven't changed just to release a "global" version. 4. I'd like to have my development environment be cohesive after a release (i.e. point to my local repositiories SNAPSHOTS for the sub-project inter-dependencies).. Has anyone ever tried to do something like this? I've found: http://out-println.blogspot.com/2008/10/maven-modules-with-independent-versions.html but that scheme doesn't support wish 4 as far as I can tell. Daryl - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Integrate Maven Plugin Code (Mojo's) into Application
On 9 March 2011 12:25, Karl Heinz Marbaise wrote: > Hi Stuart, > > first thanks for your answer > > > Stuart McCulloch wrote: > > > > Looks like a known Surefire bug when using TestNG - recent releases of > > TestNG include Guice 2 as a dependency and it leaks onto the test > > classpath. > > Guice 2 doesn't have JSR330 support, hence the error (it only looks for > > Guice's BindingAnnotation, and doesn't see the javax.inject.Qualifier > > annotation) > > > > Solution is to use this configuration for now: > > > > > > maven-surefire-plugin > > 2.7.2 > > > > false > > > > > > > > I have tried that...may be i missed to mention that my tests where it > failed > are integration tests (via maven-failsafe-plugin) but tried the > configuration there as well and the result was sadly the same ...it doesn't > work. > > However ...may be the reason for not working is that my application uses > guice 2.0 as well.. In that case you could consider upgrading your application to use Guice 3.0 rc3... otherwise you'll need to somehow isolate your application's use of Guice 2 from the embedded Maven instance (this is "business as usual" for any embedded scenario - whenever you leak classes from your host classpath onto the embedded classpath there's a danger of incompatibility, hence the need for custom webapp classloaders and OSGi). > Kind regards > Karl Heinz Marbaise > > > - > Kind regards > Karl Heinz Marbaise > > http://www.soebes.de > http://www.skmwiki.de > http://supose.org/wiki/supose > -- > View this message in context: > http://maven.40175.n5.nabble.com/Integrate-Maven-Plugin-Code-Mojo-s-into-Application-tp3397120p3415401.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 > -- Cheers, Stuart
Re: Integrate Maven Plugin Code (Mojo's) into Application
Hi Stuart, first thanks for your answer Stuart McCulloch wrote: > > Looks like a known Surefire bug when using TestNG - recent releases of > TestNG include Guice 2 as a dependency and it leaks onto the test > classpath. > Guice 2 doesn't have JSR330 support, hence the error (it only looks for > Guice's BindingAnnotation, and doesn't see the javax.inject.Qualifier > annotation) > > Solution is to use this configuration for now: > > > maven-surefire-plugin > 2.7.2 > > false > > > I have tried that...may be i missed to mention that my tests where it failed are integration tests (via maven-failsafe-plugin) but tried the configuration there as well and the result was sadly the same ...it doesn't work. However ...may be the reason for not working is that my application uses guice 2.0 as well.. Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/Integrate-Maven-Plugin-Code-Mojo-s-into-Application-tp3397120p3415401.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven subversion
First, this message belongs to the user list, so redirecting there. For your question, take a look at SCM for Subversion[1]. [1] http://maven.apache.org/scm/subversion.html Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Wed, Mar 9, 2011 at 11:27 AM, anjana wrote: > hii > i m working on maven and subversion > > To Have to set up my maven project so that the scm configuration(in pom.xml > file) points to a local repository > > i have seen an example to do this from the following site: > > http://www.chrissearle.org/node/296 http://www.chrissearle.org/node/296 [ > http://www.chrissearle.org/node/296 ^ ] > > but in this example i m unable to understand the scm tag and their sub tags > how can i implement this... > do u have any solution for this problem > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-subversion-tp3415264p3415264.html > Sent from the Maven - Issues mailing list archive at Nabble.com. > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: changes:jira-report - No report for missing PID
Thanks for your help. I got the pid of my jira project from the jira team, and got it working by specifying something like: http://jira.codehaus.org/browse/MCHANGES?pid=11212 -Komal -- View this message in context: http://maven.40175.n5.nabble.com/changes-jira-report-No-report-for-missing-PID-tp3413891p3415364.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Issue with mvn3 timestamp snapshots being downloaded in local repository
Hi, Yann Albou wrote: > @Jörg : we had the same issue with the class-path of the manifest. to > resolve it you have to add useUniqueVersions to false to all archives > (jar, ejb, war...): > >> Thanks, never recognized this setting ... - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.orgorg.apache.maven.plugins >maven-jar-plugin >> >> >> >true >false >
Re: Issue with mvn3 timestamp snapshots being downloaded in local repository
Wayne Fay wrote: > > That would be the correct next step. But again, I'm not making any > statements as to whether or not this will actually occur. It will need > to be discussed on the Dev list and in the Jira. > > I can think of an awful lot of reasons why this should not be > implemented -- for one, changing the file name will break the > manifest.mf in the archive and possibly other similar files. And I'm > not sure the positive side effects of such a change would outweigh the > negative ones. > I created the jira http://jira.codehaus.org/browse/MNG-5037 Regarding the break of the manifest.mf it is already the case: By defaut, and for those that use the class-path entry, the manifest contains references to timestamped jars, but the ear/war contains snapshots jars. So your application won't work. You can bypass this behaviour by configuring the archiver as I said in my previous post. -- View this message in context: http://maven.40175.n5.nabble.com/Issue-with-mvn3-timestamp-snapshots-being-downloaded-in-local-repository-tp3408008p3415143.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
