Re: Unwanted jars getting copied

[Sumit Teke]

 You can either use config parameters under dependency plugin

*excludeArtifactIds 
* 
	String 	2.0 	Comma separated list of Artifact names too exclude.
*excludeGroupIds 
* 
	String 	2.0 	Comma separated list of GroupId Names to exclude.
*excludeScope 
* 
	String 	2.0 	Scope to exclude. An Empty string indicates no scopes 
(default).
*excludeTransitive 
* 
	boolean 	2.0 	If we should exclude transitive dependencies

*Default value is*: false.
*excludeTypes 
* 
	String 	2.0 	Comma Separated list of Types to exclude. Empty String 
indicates don't exclude anything (default).



or

in pom define dependency as


xxx.com
xxx
1.0


com.sun
tools




Thanks,
Sumit Teke
Omniscient Software Pvt Ltd
T. +91-20-26680814, Ext. 217
F. +91-20-26680815, Ext. 212
M. +91-9975709032
E. sumit_t...@omniscient.co.in

On Monday 28 February 2011 12:23 PM, Fuke, Amol wrote:

  Hi All ,



  I am using below snippet to copy dependant jars from lib to war. But

  this

also copying some unwanted jars like rt.jar and tools.jar.



  Is there any way I exclude them from getting copied into my war.





  

  maven-dependency-plugin

  

  

  install

  

  copy-dependencies

  

  

  ${project.build.directory}/lib

  

  

  

  



  Thanks,

  Amol

Clarification on Central Sync Requirements

[Peter Niederwieser]

According to (1), every POM must have elements like ,  and
. So far I've always put such information into the parent only.
Is this good enough, or do you expect us to physically put this information
into every single POM?

Cheers,
Peter

(1)
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement

-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Clarification-on-Central-Sync-Requirements-tp3402730p3402730.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

Unwanted jars getting copied

[Fuke, Amol]

 Hi All ,

 

 I am using below snippet to copy dependant jars from lib to war. But 

 this

also copying some unwanted jars like rt.jar and tools.jar.

 

 Is there any way I exclude them from getting copied into my war.

 

 

 

 maven-dependency-plugin

 

 

 install

 

 copy-dependencies

 

 

 ${project.build.directory}/lib

 

 

 

 

 

 Thanks,

 Amol

 

Re: Cannot retrieve parent snapshot pom, but can depend on it - why?

[sebb]

On 27 February 2011 21:01, Stevo Slavić  wrote:
> snapshotRepository element is available only in distributionManagement
> (see maven pom XSD here http://maven.apache.org/xsd/maven-4.0.0.xsd )
> and in it you define destination repository where snapshots of your
> project should be released - it has nothing to do with resolving
> dependencies tho. For snapshot dependencies including parent pom
> references to be resolved you need to define a dependency repository
> with snapshots enabled. E.g. [1] worked for me with maven 3.0.2 and
> I'm pretty sure you won't have problems resolving dependencies (parent
> or regular) with this configuration with maven 2.2.1 either.

Thanks - yes, I did get the download/upload repository definitions
mixed up, and your fix does work with M2.2.1.

I see now what the problem is.

The commons-parent pom depends on the Apache pom, which is where the
Apache snapshot repo is defined.

For non-snapshot commons-parent versions, Maven itself provides the
repo definition, so the Apache pom is not needed, and Maven can
download an updated version of commons-parent.

But for snapshots, Maven does not know how to find snapshot repo which
contains commons-parent, so cannot find the pom.

One way to resolve this would be to add the snapsot repo (download)
definition to the local settings.xml.
This would then allow Maven to download without needing the Apache pom.
I've tried, and that works.

Thanks for helping solve the issue.

> Regards,
> Stevo.
>
>
> [1] pom.xml with apache.snapshots dependency repository defined
>
> 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/maven-4.0.0.xsd";>
>  4.0.0
>  
>    org.apache.commons
>    commons-parent
>    19-SNAPSHOT
>  
>  foo
>  bar
>  0.0.1-SNAPSHOT
>  
>    
>      apache.snapshots.https
>      Apache Development Snapshot Repository
>      https://repository.apache.org/content/repositories/snapshots
>      
>        true
>        always
>      
>    
>  
> 
>
>
> On Sun, Feb 27, 2011 at 3:47 PM, sebb  wrote:
>> On 27 February 2011 13:41, Stevo Slavić  wrote:
>>> I doubt it is intentional behavior. You didn't mention which version
>>> of maven are you using, or maven-dependency-plugin - like with any OSS
>>> project, latest maven is the greatest, and configure plugin version in
>>> pluginManagement section. You also didn't provide snapshots repository
>>> definition snippet - maybe you're affected by default daily
>>> updatePolicy for snapshots; configure "always" or use -U switch when
>>> building.
>>
>> I'm using Maven 2.2.1
>> dependency plugin 2.0
>>
>> Not sure how I can update the plugin version (there is a 2.2), as it
>> appears that Maven tries to process the parent before it processes the
>> pluginManagement section.
>>
>> 
>>  apache.snapshots.https
>>  Apache Development Snapshot Repository
>>  https://repository.apache.org/content/repositories/snapshots
>> 
>>
>> I don't think the update policy is relevant, otherwise why would a
>> plain dependency work?
>> Anyway, I have just tried -U and that did not help
>>
>> Here is the parent.xml file in case you want to try for yourself:
>>
>> 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
>>    
>>        org.apache.commons
>>        commons-parent
>>        19-SNAPSHOT
>>    
>>
>>  org.home.mvnsample
>>  mvnsample
>>  jar
>>  1.0-SNAPSHOT
>>  mvnsample
>>  http://maven.apache.org
>> 
>>
>>> Regards,
>>> Stevo.
>>>
>>> On Sun, Feb 27, 2011 at 2:44 AM, sebb  wrote:
 I uploaded commons-parent POM 19-SNAPSHOT to the snapshot repo [1],
 and then deleted it from my local repo (because I want to test how it
 will work for others).

 When I try to depend on it as a parent, i.e.

    
        org.apache.commons
        commons-parent
        19-SNAPSHOT
    

 I get the following error:

 [INFO] Scanning for projects...
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] Error building POM (may not be this project's POM).

 Project ID: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT

 Reason: Cannot find parent: org.apache.commons:commons-parent for
 project: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT for project
 org.home.mvnsample:mvnsample:jar:1.0-
 SNAPSHOT

 Yet when the POM depends on it as a dependency, i.e.

    
      org.apache.commons
      commons-parent
      19-SNAPSHOT
      pom
    

 it is downloaded without a problem.

 It looks as though Maven does not check snapshot repositories for a
 

[ANN] Maven Assembly Plugin 2.2.1 Released

[Dennis Lundberg]

The Maven team is pleased to announce the release of the Maven Assembly
Plugin, version 2.2.1

Do you want to create a binary distribution from a Maven project that
includes supporting scripts, configuration files, and all runtime
dependencies? You need to use the Assembly Plugin to create a
distribution for your project.

http://maven.apache.org/plugins/maven-assembly-plugin/

You should specify the version in your project's plugin configuration:


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



Release Notes - Maven 2.x Assembly Plugin - Version 2.2.1

** Bug
* [MASSEMBLY-255] - Typo in error message
* [MASSEMBLY-472] - Doc includes gz but plugin
doesn't support it
* [MASSEMBLY-510] - leading period ('.') added to directory names
* [MASSEMBLY-514] - The value for prerequisites/maven in the pom.xml
should be 2.2.1 for Maven Assembly Plugin 2.2
* [MASSEMBLY-516] - Error in Example for sharing-descriptors?
* [MASSEMBLY-519] - Documentation problem: description of how to
share assemble descriptors is wrong
* [MASSEMBLY-527] - [REGRESSION] Sharing assembly descriptors
doesn't work any more
* [MASSEMBLY-528] - FileSet does not support filtering (again)
* [MASSEMBLY-534] - Doc unclear on descriptor refs
* [MASSEMBLY-538] - filtering broken in files containing '@'
* [MASSEMBLY-540] - Web site uses the 1.1.0.xsd but 1.1.2 recommended

** Improvement
* [MASSEMBLY-512] - Plugin documentation refers to "Maven 2"
* [MASSEMBLY-522] - Thread safety
* [MASSEMBLY-524] - Make recommended goal usage more explicit;
separate non-deprecated goals from deprecated ones explicitly
* [MASSEMBLY-541] - XSD for component
* [MASSEMBLY-545] - While loading multiple Filter files, already
known filter values are not applied (see MSHARED-177)


Enjoy,

-The Maven team

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

[ANN] Maven Resources Plugin 2.5 Released

[Dennis Lundberg]

The Maven team is pleased to announce the release of the Maven Resources
Plugin, version 2.5

The Resources Plugin handles the copying of project resources to the
output directory.

http://maven.apache.org/plugins/maven-resources-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-resources-plugin
  2.5



Release Notes - Maven 2.x Resources Plugin - Version 2.5

** Bug
* [MRESOURCES-104] - while filtering resources the token replacement
stops at the character @
* [MRESOURCES-110] - escapeString is broken - break filtered output

** Improvement
* [MRESOURCES-122] - Documentation improvements

** New Feature
* [MRESOURCES-128] - Custom resource filters

** Task
* [MRESOURCES-135] - Update to maven-filtering 1.0


Enjoy,

-The Maven team

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

[ANN] Maven Remote Resources Plugin 1.2 Released

[Dennis Lundberg]

The Maven team is pleased to announce the release of the Maven Remote
Resources Plugin, version 1.2

This plugin is used to retrieve JARs of resources from remote
repositories, process those resources, and incorporate them into JARs
you build with Maven.

http://maven.apache.org/plugins/maven-remote-resources-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-remote-resources-plugin
  1.2



Release Notes - Maven 2.x Remote Resources Plugin - Version 1.2

** Bug
* [MRRESOURCES-48] - Velocimacros included with #parse() are
sometimes ignored
* [MRRESOURCES-51] - Publish the XML schemas for remote-resources
and supplemental-model

** Improvement
* [MRRESOURCES-46] - project.properties not default provided to
velocity for interpolation
* [MRRESOURCES-50] - Add @threadSafe support for maven3


** Task
* [MRRESOURCES-52] - Update to maven-filtering 1.0


Enjoy,

-The Maven team

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

Re: Cannot retrieve parent snapshot pom, but can depend on it - why?

[Stevo Slavić]

snapshotRepository element is available only in distributionManagement
(see maven pom XSD here http://maven.apache.org/xsd/maven-4.0.0.xsd )
and in it you define destination repository where snapshots of your
project should be released - it has nothing to do with resolving
dependencies tho. For snapshot dependencies including parent pom
references to be resolved you need to define a dependency repository
with snapshots enabled. E.g. [1] worked for me with maven 3.0.2 and
I'm pretty sure you won't have problems resolving dependencies (parent
or regular) with this configuration with maven 2.2.1 either.

Regards,
Stevo.


[1] pom.xml with apache.snapshots dependency repository defined

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/maven-4.0.0.xsd";>
  4.0.0
  
org.apache.commons
commons-parent
19-SNAPSHOT
  
  foo
  bar
  0.0.1-SNAPSHOT
  

  apache.snapshots.https
  Apache Development Snapshot Repository
  https://repository.apache.org/content/repositories/snapshots
  
true
always
  

  



On Sun, Feb 27, 2011 at 3:47 PM, sebb  wrote:
> On 27 February 2011 13:41, Stevo Slavić  wrote:
>> I doubt it is intentional behavior. You didn't mention which version
>> of maven are you using, or maven-dependency-plugin - like with any OSS
>> project, latest maven is the greatest, and configure plugin version in
>> pluginManagement section. You also didn't provide snapshots repository
>> definition snippet - maybe you're affected by default daily
>> updatePolicy for snapshots; configure "always" or use -U switch when
>> building.
>
> I'm using Maven 2.2.1
> dependency plugin 2.0
>
> Not sure how I can update the plugin version (there is a 2.2), as it
> appears that Maven tries to process the parent before it processes the
> pluginManagement section.
>
> 
>  apache.snapshots.https
>  Apache Development Snapshot Repository
>  https://repository.apache.org/content/repositories/snapshots
> 
>
> I don't think the update policy is relevant, otherwise why would a
> plain dependency work?
> Anyway, I have just tried -U and that did not help
>
> Here is the parent.xml file in case you want to try for yourself:
>
> 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
>    
>        org.apache.commons
>        commons-parent
>        19-SNAPSHOT
>    
>
>  org.home.mvnsample
>  mvnsample
>  jar
>  1.0-SNAPSHOT
>  mvnsample
>  http://maven.apache.org
> 
>
>> Regards,
>> Stevo.
>>
>> On Sun, Feb 27, 2011 at 2:44 AM, sebb  wrote:
>>> I uploaded commons-parent POM 19-SNAPSHOT to the snapshot repo [1],
>>> and then deleted it from my local repo (because I want to test how it
>>> will work for others).
>>>
>>> When I try to depend on it as a parent, i.e.
>>>
>>>    
>>>        org.apache.commons
>>>        commons-parent
>>>        19-SNAPSHOT
>>>    
>>>
>>> I get the following error:
>>>
>>> [INFO] Scanning for projects...
>>> [INFO] 
>>> 
>>> [ERROR] FATAL ERROR
>>> [INFO] 
>>> 
>>> [INFO] Error building POM (may not be this project's POM).
>>>
>>> Project ID: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT
>>>
>>> Reason: Cannot find parent: org.apache.commons:commons-parent for
>>> project: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT for project
>>> org.home.mvnsample:mvnsample:jar:1.0-
>>> SNAPSHOT
>>>
>>> Yet when the POM depends on it as a dependency, i.e.
>>>
>>>    
>>>      org.apache.commons
>>>      commons-parent
>>>      19-SNAPSHOT
>>>      pom
>>>    
>>>
>>> it is downloaded without a problem.
>>>
>>> It looks as though Maven does not check snapshot repositories for a
>>> parent POM dependency.
>>> Is this true, and if so is it intentional?
>>>
>>> [1] 
>>> http://repository.apache.org/snapshots/org/apache/commons/commons-parent/19-SNAPSHOT/
>>>
>>> -
>>> 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
>
>

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

Re: Assembly plugin to produce an EAR archive

[Celinio]

ok.
Someone knows a good example of the use of that assembly plugin with a multiple 
modules project ?


--- On Sat, 2/26/11, Anders Hammar  wrote:

From: Anders Hammar 
Subject: Re: Assembly plugin to produce an EAR archive
To: "Maven Users List" 
Date: Saturday, February 26, 2011, 7:17 AM

Normally, you ear plugin should fit your needs. If it turns out not to do
all you want it to do, then possibly look at the assembly plugin.

/Anders

On Sat, Feb 26, 2011 at 16:11, Celinio  wrote:

> Hi,
> I have this multiple module project where one module is the parent and 2
> other modules are children.
> One child module produces a JAR and the other child module produces a WAR
> archive (webapp).
>
> I would like to use the assembly plugin to join these 2 archives inside an
> EAR archive.
> Is there some example / tutorial out there ?
>
> I know there is also an EAR plugin but i'm still evaluating / testing these
> plugins so i am interested to know which one is best for this situation.
>
> Any idea ?
> Thanks for helping.
>
>
>
>



  

[ANN] Aspectj-maven-plugin-1.3.1 Released

[Robert Scholte]

Hi,

The Mojo team is pleased to announce the release of the Aspectj Maven Plugin 
version 1.3.1. 

This plugin handles AspectJ usage with maven. Functionality provided is: 
weaving of aspects (or existing aspects from libraries) with the test and/or 
main classes, weaving of pre-existing jars and ajdoc reporting. 
http://mojo.codehaus.org/aspectj-maven-plugin

To get this update, simply specify the version in your project's plugin 
configuration: 


org.codehaus.mojo
aspectj-maven-plugin
1.3.1


ADDITIONAL_INFORMATION

Release Notes - Mojo AspectJ Plugin - Version 1.3.1  Bug[MASPECTJ-16] - 
 must support  (and ) [MASPECTJ-82] - Upgrade 
plugin to use aspectj 1.6.8 (actually 1.6.10)[MASPECTJ-86] - Allow compilation 
of weaveDependency when no sources are present in the project [MASPECTJ-90] - 
Classpath on aspectJ plugin doesn't respect the dependencies order

Enjoy,

The Mojo team.

-Robert Scholte   

Re: Comparing dependency trees

[Baptiste MATHUS]

Yup, maybe this is an idea for a new goal like dependency:compare.

Currently, the only solution I know is the one Wayne described.

Cheers

2011/2/25 Paul Grove 

> Wayne,
>
> Thanks for the response, diff is one solution but still to manual for my
> liking. We are using WAR overlays as a sort of deployment description of
> our
> application as we have lots of components that can be changed for each
> deployment for different customers based around a core product. What I want
> to do is when we do a new deployment for an existing deployment we can
> produce some report showing what dependencies have changed version, what
> have been removed and what has been added.
>
> Seems like an extension to the dependency plugin to me?
>
> Paul
>
> On 25 February 2011 04:17, Wayne Fay  wrote:
>
> > > Is there a way of comparing the dependency tree of 2 version of the
> same
> > POM
> > > and printing out the differences?
> >
> > Other than something like this (below), I don't know of any way to do
> this.
> >
> > mvn dependency:tree > 1.txt
> > mvn dependency:tree -f pom-old.xml > 2.txt
> > diff 1.txt 2.txt
> >
> > Wayne
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Re: Fitnesse support?

[Nick Klauer]

I've always used trinidad for my maven/fitnesse integration.

http://fitnesse.info/trinidad


-Nick Klauer


On Sun, Feb 20, 2011 at 23:32, Anders Hammar  wrote:

> This already existing ticket for the fitnesse plugin would be of interest:
> http://jira.codehaus.org/browse/MFITNESSE-30
>
> It's not a proper patch, but seems to be a fix. You should move this
> discussion to the mojo list if you want to follow up.
>
> /Anders
>
> On Sun, Feb 20, 2011 at 20:47, Thomas Sundberg  wrote:
>
> > Hi!
> >
> > I have found two different Maven plugions, but none seem to be updated
> > and supporting the latest Fitnesse release.
> >
> > The
> >
> > org.codehaus.mojo
> > fitnesse-maven-plugin
> > 1.0
> >
> > depends on
> >
> > org.fitnesse
> > fitnesse
> > 20050731
> >
> > That is a release that is five years old.
> >
> > I'm looking for a Fitnesse plugin that is maintained and supports a
> > fairly recent Fitnesse release. If I can't find, I will have to build
> > something on my own, but I would like to try to find anything updated.
> >
> > /Thomas
> >
> >
> > On Sun, Feb 20, 2011 at 18:10, Baptiste MATHUS  wrote:
> > > Hi,
> > >
> > > As running http://www.google.fr/search?q=maven+fitnesse+plugin shows
> the
> > > FitNesse Maven Plugin first (
> > http://mojo.codehaus.org/fitnesse-maven-plugin/),
> > > why didn't you directly try to explain precisely what you're missing in
> > this
> > > dedicated plugin?
> > >
> > > Cheers
> > >
> > > 2011/2/20 Thomas Sundberg 
> > >
> > >> Hi!
> > >>
> > >> Does anybody know of any good Maven plugins that support running
> > >> Fitnesse acceptance tests? I have done some research and as far as I
> > >> can see, there doesn't exist any up to date solutions.
> > >>
> > >> Any tip is highly appreciated.
> > >>
> > >> /Thomas
> > >>
> > >> --
> > >> 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
> > >>
> > >>
> > >
> > >
> > > --
> > > Baptiste  MATHUS - http://batmat.net
> > > Sauvez un arbre,
> > > Mangez un castor !
> > >
> >
> >
> >
> > --
> > 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: Cannot retrieve parent snapshot pom, but can depend on it - why?

[sebb]

On 27 February 2011 13:41, Stevo Slavić  wrote:
> I doubt it is intentional behavior. You didn't mention which version
> of maven are you using, or maven-dependency-plugin - like with any OSS
> project, latest maven is the greatest, and configure plugin version in
> pluginManagement section. You also didn't provide snapshots repository
> definition snippet - maybe you're affected by default daily
> updatePolicy for snapshots; configure "always" or use -U switch when
> building.

I'm using Maven 2.2.1
dependency plugin 2.0

Not sure how I can update the plugin version (there is a 2.2), as it
appears that Maven tries to process the parent before it processes the
pluginManagement section.


  apache.snapshots.https
  Apache Development Snapshot Repository
  https://repository.apache.org/content/repositories/snapshots


I don't think the update policy is relevant, otherwise why would a
plain dependency work?
Anyway, I have just tried -U and that did not help

Here is the parent.xml file in case you want to try for yourself:

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

org.apache.commons
commons-parent
19-SNAPSHOT


  org.home.mvnsample
  mvnsample
  jar
  1.0-SNAPSHOT
  mvnsample
  http://maven.apache.org


> Regards,
> Stevo.
>
> On Sun, Feb 27, 2011 at 2:44 AM, sebb  wrote:
>> I uploaded commons-parent POM 19-SNAPSHOT to the snapshot repo [1],
>> and then deleted it from my local repo (because I want to test how it
>> will work for others).
>>
>> When I try to depend on it as a parent, i.e.
>>
>>    
>>        org.apache.commons
>>        commons-parent
>>        19-SNAPSHOT
>>    
>>
>> I get the following error:
>>
>> [INFO] Scanning for projects...
>> [INFO] 
>> 
>> [ERROR] FATAL ERROR
>> [INFO] 
>> 
>> [INFO] Error building POM (may not be this project's POM).
>>
>> Project ID: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT
>>
>> Reason: Cannot find parent: org.apache.commons:commons-parent for
>> project: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT for project
>> org.home.mvnsample:mvnsample:jar:1.0-
>> SNAPSHOT
>>
>> Yet when the POM depends on it as a dependency, i.e.
>>
>>    
>>      org.apache.commons
>>      commons-parent
>>      19-SNAPSHOT
>>      pom
>>    
>>
>> it is downloaded without a problem.
>>
>> It looks as though Maven does not check snapshot repositories for a
>> parent POM dependency.
>> Is this true, and if so is it intentional?
>>
>> [1] 
>> http://repository.apache.org/snapshots/org/apache/commons/commons-parent/19-SNAPSHOT/
>>
>> -
>> 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

Import-scope-like behavior for plugins

[Stevo Slavić]

Hello Apache Maven users,

Is there a way to achieve behavior similar to import scope for
dependencies, but for plugins, without inheriting another project?

Would like to create pom projects with set of plugins with latest
versions configured, one for each frequently used plugin provider
(e.g. pom for apache maven core plugins, another pom for codehaus
maven mojos, etc.) and then import these poms in plugin management.

Regards,
Stevo.

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

Re: Cannot retrieve parent snapshot pom, but can depend on it - why?

[Stevo Slavić]

I doubt it is intentional behavior. You didn't mention which version
of maven are you using, or maven-dependency-plugin - like with any OSS
project, latest maven is the greatest, and configure plugin version in
pluginManagement section. You also didn't provide snapshots repository
definition snippet - maybe you're affected by default daily
updatePolicy for snapshots; configure "always" or use -U switch when
building.

Regards,
Stevo.

On Sun, Feb 27, 2011 at 2:44 AM, sebb  wrote:
> I uploaded commons-parent POM 19-SNAPSHOT to the snapshot repo [1],
> and then deleted it from my local repo (because I want to test how it
> will work for others).
>
> When I try to depend on it as a parent, i.e.
>
>    
>        org.apache.commons
>        commons-parent
>        19-SNAPSHOT
>    
>
> I get the following error:
>
> [INFO] Scanning for projects...
> [INFO] 
> 
> [ERROR] FATAL ERROR
> [INFO] 
> 
> [INFO] Error building POM (may not be this project's POM).
>
> Project ID: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT
>
> Reason: Cannot find parent: org.apache.commons:commons-parent for
> project: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT for project
> org.home.mvnsample:mvnsample:jar:1.0-
> SNAPSHOT
>
> Yet when the POM depends on it as a dependency, i.e.
>
>    
>      org.apache.commons
>      commons-parent
>      19-SNAPSHOT
>      pom
>    
>
> it is downloaded without a problem.
>
> It looks as though Maven does not check snapshot repositories for a
> parent POM dependency.
> Is this true, and if so is it intentional?
>
> [1] 
> http://repository.apache.org/snapshots/org/apache/commons/commons-parent/19-SNAPSHOT/
>
> -
> 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