Re: Dependency version properties defined in settings.xml are not being resolved, Maven 2.2.1

[Anders Hammar]

You should always ensure that you have a default value for properties
set by profiles. Most likely you're running into some scenario where
the profile just isn't active.
So, in your pom you should define the property as well.

May I also add that what you're trying to do is not good. IMHO you
should never alter dependencies through profiles as this will cause
problem for people consuming your artifact. As well as for people
trying to build your project as they would get a different result
(different dependency).

/Anders

On Sat, Oct 1, 2011 at 02:55,   wrote:
>
> Using Maven 2.2.1
> I have defined a profile in my settings.xml file, and specified some
> properties. This profile is also listed as an active profile.
>
> For example:
>            
>                  third-party-lib-versions
>                  
>                        1.2.16
>                  
>            
>            
>                  third-party-lib-versions
>            
>
> Then I have a dependency in my pom, which references the property:
>
>        
>            log4j
>            log4j
>            ${log4j.version}
>        
>
> In most cases Maven 2.2.1 will inject the property just fine. But it seems
> to also end up creating a $M2_REPO/log4j/log4j/${log4j.version}, and when I
> run "mvn test", it complains
> [INFO] Unable to find resource 'log4j:log4j:pom:${log4j.version}' in
> repository central (xxx)
>
> Is there something else that I need to do to ensure that properties defined
> in settings.xml are always processed ?
>
> Thanks
> Aspi Engineer
> Putnam Investments
>
>
>
> This message is intended for the recipient only and is not meant to be 
> forwarded or distributed in any other format. This communication is for 
> informational purposes only. It is not intended as an offer or solicitation 
> for the purchase or sale of any financial instrument, or security, or as an 
> official confirmation of any transaction. Putnam does not accept purchase or 
> redemptions of securities, instructions, or authorizations that are sent via 
> e-mail. All market prices, data and other information are not warranted as to 
> completeness or accuracy and are subject to change without notice. Any 
> comments or statements made herein do not necessarily reflect those of Putnam 
> Investments, LLC (DBA Putnam Investments) and its subsidiaries and 
> affiliates. If you are not the intended recipient of this e-mail, please 
> delete the e-mail.
>
> -
> 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

Dependency version properties defined in settings.xml are not being resolved, Maven 2.2.1

[Aspi_Engineer]

Using Maven 2.2.1
I have defined a profile in my settings.xml file, and specified some
properties. This profile is also listed as an active profile.

For example:

  third-party-lib-versions
  
1.2.16
  


  third-party-lib-versions


Then I have a dependency in my pom, which references the property:


log4j
log4j
${log4j.version}


In most cases Maven 2.2.1 will inject the property just fine. But it seems
to also end up creating a $M2_REPO/log4j/log4j/${log4j.version}, and when I
run "mvn test", it complains
[INFO] Unable to find resource 'log4j:log4j:pom:${log4j.version}' in
repository central (xxx)

Is there something else that I need to do to ensure that properties defined
in settings.xml are always processed ?

Thanks
Aspi Engineer
Putnam Investments



This message is intended for the recipient only and is not meant to be 
forwarded or distributed in any other format. This communication is for 
informational purposes only. It is not intended as an offer or solicitation for 
the purchase or sale of any financial instrument, or security, or as an 
official confirmation of any transaction. Putnam does not accept purchase or 
redemptions of securities, instructions, or authorizations that are sent via 
e-mail. All market prices, data and other information are not warranted as to 
completeness or accuracy and are subject to change without notice. Any comments 
or statements made herein do not necessarily reflect those of Putnam 
Investments, LLC (DBA Putnam Investments) and its subsidiaries and affiliates. 
If you are not the intended recipient of this e-mail, please delete the e-mail.

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

Re: Insert a timestamp into an archetype?

[Bram Patelski]

Okay, I see.

Well, I'm not sure if there is a filter-option for current time.
I did once write a custom mojo for renaming packages (so directories) based
on the archetype artifactId.
That way if I used the archetype to generate a new project called:
- groupId: org.apache.whatever
- artifactId: myNewProject
I could auto-rename my class-package to:
org.apache.whatever.myNewProject

I also had the idea (didn't make it... yet?) of writing a mojo for filtering
Word-templates of the documentation.
Maybe you could use an approach like this. Obviously you have "new Date()"
at your disposal if you write your own mojo.
But it would be cleaner to have the filter-option like you tried.

Good luck

On Fri, Sep 30, 2011 at 23:21, Dennis Lundberg  wrote:

> Hi Bram
>
> Thanks for your suggestion. My current approach is to use filtering to
> insert the timestamp into the .java file.
>
> The problem I am having is actually getting hold of the appropriate
> value of a timestamp. It should reflect the point in time when my
> archetype is used to generate a new project.
>
> On 2011-09-30 22:03, Bram Patelski wrote:
> > You could use filtering?
> >
> > On Fri, Sep 30, 2011 at 22:01, Dennis Lundberg 
> wrote:
> >
> >> Hi
> >>
> >> I'm creating an archetype, with a bunch of files. In the .java files I
> >> want to insert a timestamp. When I use the archetype to generate a new
> >> project, the .java files should show when they were generated.
> >>
> >> Is this possible?
> >>
> >> I have tried inserting ${maven.build.timestamp} as the default value in
> >> my archetype-metadata.xml file, but it doesn't seem to work.
> >>
> >> --
> >> Dennis Lundberg
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
>
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Maven not pulling down latest snapshot jar issue

[Patrick Sansoucy]

My pleasure,

Since M2 does the job, most people I've spoken to (including at my own
workplace) hold back on M3 ... On top of that, there is the
timestamped artifact workaround.

I wish this could be higher up in the priority list, just for the fact
it will push M3 adoption :(

Patrick Sansoucy
In theory, there is no difference between theory and practice, but in
practice, there is ...



On Fri, Sep 30, 2011 at 5:24 PM, Kurt T Stam  wrote:
> Thanks Patrick,
>
> Yep that one is just what I am seeing. Looks like there is more to it then I
> thought.. Thanks for pointing me in the right direction.. Why aren't more
> people complaining about this? Is everyone using products like Artifactory
> to keep the number of snapshot of each artifact down?
>
> --Kurt
>
> On 9/30/11 3:42 PM, Patrick Sansoucy wrote:
>>
>> Is'nt rather related to this Jira that's been there for a while ?
>>
>>
>> http://jira.codehaus.org/browse/MNG-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>
>>
>> Patrick Sansoucy
>> In theory, there is no difference between theory and practice, but in
>> practice, there is ...
>>
>>
>>
>> On Fri, Sep 30, 2011 at 2:44 PM, Kurt T Stam  wrote:
>>>
>>> Thanks Robert,
>>>
>>> I tried replacing the aether jar from 1.11 to 1.12 but that did not fix
>>> my
>>> issue. In my case the meta
>>> data is nicely updated by the actual jar and pom etc are still old.
>>>
>>> I guess I will spend some time with the debugger over the weekend to see
>>> what's going on.
>>>
>>> If anyone has some hints in where to look first then plz let me know!
>>>
>>> --Kurt
>>>
>>> On 9/30/11 12:40 PM, Robert Scholte wrote:

 Sounds like http://jira.codehaus.org/browse/MNG-5087



 -Robert


> Date: Fri, 30 Sep 2011 11:46:19 -0400
> From: kurt.s...@gmail.com
> To: users@maven.apache.org
> Subject: Maven not pulling down latest snapshot jar issue
>
> 1. I'm using maven-3.0.3 and does anyone else have the issue where the
> latest
> snapshot jar is NOT downloaded while the meta data IS updated?
>
> It sounds a lot like what's being described in this bug report,
> although
> the title is misleading
> http://jira.codehaus.org/browse/MNG-4142, ad it happens when
>
> false
>
> for that repository.
>
> 2. I tried applying the patch attached to MNG-4142 to the current
> trunk,
> but code seems to have been moved around on the trunk. Maybe someone
> can
> point to the current relevant code, so I can maybe submit a patch for
> it. This issue is pretty nasty as it makes for non reproducible builds.
>
> Thx,
>
> --Kurt
>
>
> -
> 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
>>
>
>
> -
> 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: Maven not pulling down latest snapshot jar issue

[Kurt T Stam]

Thanks Patrick,

Yep that one is just what I am seeing. Looks like there is more to it 
then I thought.. Thanks for pointing me in the right direction.. Why 
aren't more people complaining about this? Is everyone using products 
like Artifactory to keep the number of snapshot of each artifact down?


--Kurt

On 9/30/11 3:42 PM, Patrick Sansoucy wrote:

Is'nt rather related to this Jira that's been there for a while ?

http://jira.codehaus.org/browse/MNG-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel


Patrick Sansoucy
In theory, there is no difference between theory and practice, but in
practice, there is ...



On Fri, Sep 30, 2011 at 2:44 PM, Kurt T Stam  wrote:

Thanks Robert,

I tried replacing the aether jar from 1.11 to 1.12 but that did not fix my
issue. In my case the meta
data is nicely updated by the actual jar and pom etc are still old.

I guess I will spend some time with the debugger over the weekend to see
what's going on.

If anyone has some hints in where to look first then plz let me know!

--Kurt

On 9/30/11 12:40 PM, Robert Scholte wrote:

Sounds like http://jira.codehaus.org/browse/MNG-5087



-Robert



Date: Fri, 30 Sep 2011 11:46:19 -0400
From: kurt.s...@gmail.com
To: users@maven.apache.org
Subject: Maven not pulling down latest snapshot jar issue

1. I'm using maven-3.0.3 and does anyone else have the issue where the
latest
snapshot jar is NOT downloaded while the meta data IS updated?

It sounds a lot like what's being described in this bug report, although
the title is misleading
http://jira.codehaus.org/browse/MNG-4142, ad it happens when

false

for that repository.

2. I tried applying the patch attached to MNG-4142 to the current trunk,
but code seems to have been moved around on the trunk. Maybe someone can
point to the current relevant code, so I can maybe submit a patch for
it. This issue is pretty nasty as it makes for non reproducible builds.

Thx,

--Kurt


-
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




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

Re: Insert a timestamp into an archetype?

[Dennis Lundberg]

Hi Bram

Thanks for your suggestion. My current approach is to use filtering to
insert the timestamp into the .java file.

The problem I am having is actually getting hold of the appropriate
value of a timestamp. It should reflect the point in time when my
archetype is used to generate a new project.

On 2011-09-30 22:03, Bram Patelski wrote:
> You could use filtering?
> 
> On Fri, Sep 30, 2011 at 22:01, Dennis Lundberg  wrote:
> 
>> Hi
>>
>> I'm creating an archetype, with a bunch of files. In the .java files I
>> want to insert a timestamp. When I use the archetype to generate a new
>> project, the .java files should show when they were generated.
>>
>> Is this possible?
>>
>> I have tried inserting ${maven.build.timestamp} as the default value in
>> my archetype-metadata.xml file, but it doesn't seem to work.
>>
>> --
>> Dennis Lundberg
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
> 


-- 
Dennis Lundberg

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

[ANN] Maven Surefire 2.10 Released

[Paul Gier]

The Maven team is pleased to announce the release of the Maven Surefire,
version 2.10

This release includes the maven-surefire-plugin, which executes the
unit tests of an application, the maven-surefire-report-plugin, which
parses surefire/failsafe test results and renders them to DOXIA
creating the web interface version of the test results, as well as the
maven-failsafe-plugin, which executes the integration tests of an
application.

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

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


  org.apache.maven.plugins
  maven-surefire-plugin
  2.10



Release Notes - Maven Surefire - Version 2.10

** Bug
* [SUREFIRE-754] - unbounded memory use when capturing logs
* [SUREFIRE-761] - java.lang.NoSuchMethodException when trying to
run Junit 3 suite class
* [SUREFIRE-763] - environmentVariables fails with
useSystemClassLoader=false or forkMode=always
* [SUREFIRE-766] - Regression in excludes feature between surefire
2.6 and 2.7.

** Improvement
* [SUREFIRE-738] - Fail on not existing run order.
* [SUREFIRE-750] - Add custom name suffix for surefire-reports (xml
and txt)
* [SUREFIRE-752] - Fix duplication in surefire/failsafe sites

** New Feature
* [SUREFIRE-755] - Add new reports which default to the failsafe-
results


Enjoy,

-The Maven team




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

Re: Insert a timestamp into an archetype?

[Bram Patelski]

You could use filtering?

On Fri, Sep 30, 2011 at 22:01, Dennis Lundberg  wrote:

> Hi
>
> I'm creating an archetype, with a bunch of files. In the .java files I
> want to insert a timestamp. When I use the archetype to generate a new
> project, the .java files should show when they were generated.
>
> Is this possible?
>
> I have tried inserting ${maven.build.timestamp} as the default value in
> my archetype-metadata.xml file, but it doesn't seem to work.
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Insert a timestamp into an archetype?

[Dennis Lundberg]

Hi

I'm creating an archetype, with a bunch of files. In the .java files I
want to insert a timestamp. When I use the archetype to generate a new
project, the .java files should show when they were generated.

Is this possible?

I have tried inserting ${maven.build.timestamp} as the default value in
my archetype-metadata.xml file, but it doesn't seem to work.

-- 
Dennis Lundberg

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

Re: Maven not pulling down latest snapshot jar issue

[Patrick Sansoucy]

Is'nt rather related to this Jira that's been there for a while ?

http://jira.codehaus.org/browse/MNG-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel


Patrick Sansoucy
In theory, there is no difference between theory and practice, but in
practice, there is ...



On Fri, Sep 30, 2011 at 2:44 PM, Kurt T Stam  wrote:
> Thanks Robert,
>
> I tried replacing the aether jar from 1.11 to 1.12 but that did not fix my
> issue. In my case the meta
> data is nicely updated by the actual jar and pom etc are still old.
>
> I guess I will spend some time with the debugger over the weekend to see
> what's going on.
>
> If anyone has some hints in where to look first then plz let me know!
>
> --Kurt
>
> On 9/30/11 12:40 PM, Robert Scholte wrote:
>>
>> Sounds like http://jira.codehaus.org/browse/MNG-5087
>>
>>
>>
>> -Robert
>>
>>
>>> Date: Fri, 30 Sep 2011 11:46:19 -0400
>>> From: kurt.s...@gmail.com
>>> To: users@maven.apache.org
>>> Subject: Maven not pulling down latest snapshot jar issue
>>>
>>> 1. I'm using maven-3.0.3 and does anyone else have the issue where the
>>> latest
>>> snapshot jar is NOT downloaded while the meta data IS updated?
>>>
>>> It sounds a lot like what's being described in this bug report, although
>>> the title is misleading
>>> http://jira.codehaus.org/browse/MNG-4142, ad it happens when
>>>
>>> false
>>>
>>> for that repository.
>>>
>>> 2. I tried applying the patch attached to MNG-4142 to the current trunk,
>>> but code seems to have been moved around on the trunk. Maybe someone can
>>> point to the current relevant code, so I can maybe submit a patch for
>>> it. This issue is pretty nasty as it makes for non reproducible builds.
>>>
>>> Thx,
>>>
>>> --Kurt
>>>
>>>
>>> -
>>> 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: maven 3.0.3 - performance with version ranges

[Tommy Chheng]

+1 for using aether >1.12, this reduced 2:00 compile time to ~45 seconds.


2011/9/30 Tamás Cservenák 

> Take a peek at this thread (especially 1st mail):
>
> http://maven.40175.n5.nabble.com/Apache-Maven-distribution-with-fixes-td4639045.html
>
> Thanks,
> ~t~
>
> On Fri, Sep 30, 2011 at 12:22 PM, Paul French 
> wrote:
> > maven 3.0.3 has terrible performance and memory usage when using version
> > ranges. This has a knock on effect using m2e
> >
> > It takes maven ages to update the maven dependencies.
> >
> > I have a main project with a some version ranged dependencies which in
> turn
> > have versioned ranged dependencies. Outside of eclipse it takes many
> minutes
> > and considerable memory to get a successful build. Most time is spent
> > resolving the dependencies.
> >
> > I have also run maven offline when I know I have all dependencies in my
> > local repo and it is still very, very slow.
> >
> > In m2e (and workspace resolution on), you can check out a dependency that
> is
> > very simple and this triggers a re-build of the main project. The same
> > happens when you delete the dependent project or make pom version changes
> to
> > it. So in eclipse this becomes really tedious especially if you have 4 or
> 5
> > related projects checked out. You end up sitting and waiting for your
> > workspace to be re-built all the time.
> >
> > I understand what maven is doing but I do believe it could be done a lot
> > better when resolving version ranges.
> >
> > I also know maven 3.0.3 uses aether 1.11 to so its dependency management.
> >
> > I'm really keen to try and find a solution. aether 1.12 has been
> released.
> > Is there anyway I can hook this into maven 3.0.3
> >
> > Does aether 1.12 solve
> >
> > Is there a pre-release of maven 3.0.4 out there yet that I can try and
> does
> > it use aether 1.12 ?
> >
> > Thanks
> > Paul
> >
> >
> > -
> > 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
>
>


-- 
@tommychheng
http://tommy.chheng.com

Re: Maven not pulling down latest snapshot jar issue

[Kurt T Stam]

Thanks Robert,

I tried replacing the aether jar from 1.11 to 1.12 but that did not fix 
my issue. In my case the meta

data is nicely updated by the actual jar and pom etc are still old.

I guess I will spend some time with the debugger over the weekend to see 
what's going on.


If anyone has some hints in where to look first then plz let me know!

--Kurt

On 9/30/11 12:40 PM, Robert Scholte wrote:

Sounds like http://jira.codehaus.org/browse/MNG-5087



-Robert



Date: Fri, 30 Sep 2011 11:46:19 -0400
From: kurt.s...@gmail.com
To: users@maven.apache.org
Subject: Maven not pulling down latest snapshot jar issue

1. I'm using maven-3.0.3 and does anyone else have the issue where the
latest
snapshot jar is NOT downloaded while the meta data IS updated?

It sounds a lot like what's being described in this bug report, although
the title is misleading
http://jira.codehaus.org/browse/MNG-4142, ad it happens when

false

for that repository.

2. I tried applying the patch attached to MNG-4142 to the current trunk,
but code seems to have been moved around on the trunk. Maybe someone can
point to the current relevant code, so I can maybe submit a patch for
it. This issue is pretty nasty as it makes for non reproducible builds.

Thx,

--Kurt


-
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

SCM ClearCase URL Question

[Bleach, Justin]

Hi,

 

Anyone have experience with crafting a URL for  node in maven 3
pom.xml

 

I've read the brief docs on ClearCase URLs but my 'mvn scm:validate' is
not successful.

 

I have a configSpec at: c:\views\myView\configSpec.txt

 

Supposedly I'm supposed to be doing something like this:

 

scm:clearcase:myView:c|\views\myView\configSpec.txt

 

But it says it has an issue with "c|" even though the docs says to use |
in place of : for Windows paths. If I change it to : then it says
everything from c: onwards is not used, or not integral to the URL.

 

I just want it to point to the config spec, once I do apparently the
rest should be Golden.

 

Justin Bleach 

 



CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for 
the sole use of the intended recipient(s) and may contain confidential and 
privileged information or otherwise protected by law. Any unauthorized review, 
use, disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message.

Re: Help!

[GustavoR]

Thanks in advance

It works!!

I'll adopt your advices for next posts


2011/9/29 Barrie Treloar [via Maven] :
> On Fri, Sep 30, 2011 at 12:42 AM, GustavoR
> <[hidden email]> wrote:
>> Hi to everyone. That's is my first post..
>>
>> I have a big multi-module project
>>
>> Suppose that project structure:
>>
>> MainModule
>>   |_ Module1
>>   |     |_ SubModule1
>>   |_ Module 2
>>         |_SubModule2
>>
>> And SubModule2 has a dependency with SubModule1. Is there any way to run
>> mvn
>> test in Submodule2 forcing the generation of SubModule1 and its dependents
>> if it have. I dont have SubModule1 installed in my local repository.. so
>> mvn
>> test in Submodule2 fails.
> As this is your first post, I'll remind you that having a subject line
> like "Help!" will often generate no response.
> Please read http://catb.org/~esr/faqs/smart-questions.html
> You are lucky that Wayne has replied.
>
> Now, to answer the question.
>
> Have you tried?
>   mvn -h
>
> At the root level, you can run
>   mvn --also-make -pl Module2/SubModule2 test
>
> This will also build any projects that SubModule2 depends upon.
>
> An alternative is to setup your IDE correctly.
>
> If you have your IDE setup correctly (e.g. Eclipse) then for most of
> the time you can make your changes there, and run the unit tests
> inside Eclipse.
> As each project will be configured to depend upon the other projects
> it needs inside Eclipse you do not need to break out to a shell to run
> Maven all the time.
>
> You should run
>   mvn clean install
> just before you commit any changes to your repository to validate you
> haven't broken any other things that Maven will do for you, that
> Eclipse doesn't
>
> -
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>
> 
> If you reply to this email, your message will be added to the discussion
> below:
> http://maven.40175.n5.nabble.com/Help-tp4853497p4854981.html
> To unsubscribe from Help!, click here.


--
View this message in context: 
http://maven.40175.n5.nabble.com/Help-tp4853497p4857945.html
Sent from the Maven - Users mailing list archive at Nabble.com.

RE: Maven not pulling down latest snapshot jar issue

[Robert Scholte]

Sounds like http://jira.codehaus.org/browse/MNG-5087

 

-Robert


> Date: Fri, 30 Sep 2011 11:46:19 -0400
> From: kurt.s...@gmail.com
> To: users@maven.apache.org
> Subject: Maven not pulling down latest snapshot jar issue
> 
> 1. I'm using maven-3.0.3 and does anyone else have the issue where the 
> latest
> snapshot jar is NOT downloaded while the meta data IS updated?
> 
> It sounds a lot like what's being described in this bug report, although 
> the title is misleading
> http://jira.codehaus.org/browse/MNG-4142, ad it happens when
> 
> false
> 
> for that repository.
> 
> 2. I tried applying the patch attached to MNG-4142 to the current trunk, 
> but code seems to have been moved around on the trunk. Maybe someone can 
> point to the current relevant code, so I can maybe submit a patch for 
> it. This issue is pretty nasty as it makes for non reproducible builds.
> 
> Thx,
> 
> --Kurt
> 
> 
> -
> 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: Resources not included in build jar

[Bram Patelski]

Hi,

Are these empty folders? If not: They should be included in the jar
automatically.
You could also have a look at this page:
http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html

Regards,
Bram

On Fri, Sep 30, 2011 at 16:21, motes motes  wrote:

> I have created some sub folders in src/main/resources that I would
> like to include in the final artifact.jar file.
>
>
>
>
>src/main/resources/
>
>
>
>  src/main/resources/logs
>
>
>
>  src/main/resources/data
>
>
> ...
>
> Next I copy these resources to the target folder:
>
>
>
>  maven-resources-plugin
>
>
>  ${target.basedir}
>
>  true
>
>
>
>  src/main/resources
>
>
>
>
>
>copy-resources
>packaging
>
>
>  copy-resources
>
>
>
>
>
>
>
> Further I use the maven-dependency-plugin during compile time to fetch
> some dependencies from nexus and copy those the /target folder.
>
>
>
>  maven-dependency-plugin
>
>
>copy-and-unpack
>
>  generate-sources
>
>unpack
>
>
>
>
>  
>
>  com.test
>
>  assembly
>
>  1.0.1
>
>  zip
>
>  true
>
>  ${target.basedir}
>
>  
>
>
>
>
>
>
> These dependencies should also be included in the final artifact.jar
> file. But after I have run mvn clean install the artifact.jar file
> only contains the manifest file.
>
> How do I include resources from the project and target folder i the
> final artifact.jar file?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Maven not pulling down latest snapshot jar issue

[Kurt T Stam]

1. I'm using maven-3.0.3 and does anyone else have the issue where the 
latest

snapshot jar is NOT downloaded while the meta data IS updated?

It sounds a lot like what's being described in this bug report, although 
the title is misleading

http://jira.codehaus.org/browse/MNG-4142, ad it happens when

false

for that repository.

2. I tried applying the patch attached to MNG-4142 to the current trunk, 
but code seems to have been moved around on the trunk. Maybe someone can 
point to the current relevant code, so I can maybe submit a patch for 
it. This issue is pretty nasty as it makes for non reproducible builds.


Thx,

--Kurt


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

Re: Build hangs on maven site generation

[Bram Patelski]

Yes, when I run them by hand (in the jenkins checked-out workspace) it runs
fine
and most other projects run fine from Jenkins. Most failing projects worked
fine in the first place, but I always had to run the very first build by
hand. After that initial build, they would run fine, but some of them just
seem to hang. Btw: most project profiles in Jenkins, including the ones that
hang were created using copy existing project.

Thanks


On Fri, Sep 30, 2011 at 16:54, Olivier Lamy  wrote:

> is svn on the PATH ? I presume you are running change log report ?
>
> 2011/9/30 Bram Patelski :
> > Hi,
> >
> > I've replied several times to an old thread, but never got my mail
> accepted
> > by the list.
> > It concerns this thread:
> >
> http://jenkins.361315.n4.nabble.com/Build-hangs-on-maven-site-generation-td366706.html
> >
> > My post:
> > Hi,
> >
> > I have these same problems, but not on all projects/builds. As with the
> > original issue: mvn clean package works like a charm, but mvn clean
> > site-deploy does not from Jenkins. I tried to call Maven from commandline
> > and that works fine. Also: most site-deploy tasks in Jenkins work after I
> > run it once from commandline, then re-trigger the task manually.
> > I compared the poms of different projects (one that works compared to one
> > that doesn't), but can't see any differences.
> >
> > Can I check anything else to find out what's causing this?
> >
> > Working on:
> > - Windows
> > - Jenkins 1.405 (deployed as WAR on Apache Tomcat 6.0)
> > - Jenkins Subversion Plug-in 1.26
> >
> > Some more testing:
> > If I run from command-line first, I can run the Jenkins task successful
> only
> > once. If I run the Jenkins task again, it hangs:
> >
> > [INFO] SCM Command Line[0]: svn
> > [INFO] SCM Command Line[1]: log
> > [INFO] SCM Command Line[2]: -v
> > [INFO] SCM Command Line[3]: "-r{2011-05-18}:{2011-04-17}"
> >
> > Thanks
> >
>
>
>
> --
> Olivier Lamy
> Talend : http://talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Build hangs on maven site generation

[Olivier Lamy]

is svn on the PATH ? I presume you are running change log report ?

2011/9/30 Bram Patelski :
> Hi,
>
> I've replied several times to an old thread, but never got my mail accepted
> by the list.
> It concerns this thread:
> http://jenkins.361315.n4.nabble.com/Build-hangs-on-maven-site-generation-td366706.html
>
> My post:
> Hi,
>
> I have these same problems, but not on all projects/builds. As with the
> original issue: mvn clean package works like a charm, but mvn clean
> site-deploy does not from Jenkins. I tried to call Maven from commandline
> and that works fine. Also: most site-deploy tasks in Jenkins work after I
> run it once from commandline, then re-trigger the task manually.
> I compared the poms of different projects (one that works compared to one
> that doesn't), but can't see any differences.
>
> Can I check anything else to find out what's causing this?
>
> Working on:
> - Windows
> - Jenkins 1.405 (deployed as WAR on Apache Tomcat 6.0)
> - Jenkins Subversion Plug-in 1.26
>
> Some more testing:
> If I run from command-line first, I can run the Jenkins task successful only
> once. If I run the Jenkins task again, it hangs:
>
> [INFO] SCM Command Line[0]: svn
> [INFO] SCM Command Line[1]: log
> [INFO] SCM Command Line[2]: -v
> [INFO] SCM Command Line[3]: "-r{2011-05-18}:{2011-04-17}"
>
> Thanks
>



-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Resources not included in build jar

[motes motes]

I have created some sub folders in src/main/resources that I would
like to include in the final artifact.jar file.




src/main/resources/


src/main/resources/logs


src/main/resources/data


...

Next I copy these resources to the target folder:


maven-resources-plugin


${target.basedir}

true



src/main/resources





copy-resources
packaging


copy-resources







Further I use the maven-dependency-plugin during compile time to fetch
some dependencies from nexus and copy those the /target folder.


maven-dependency-plugin


copy-and-unpack
generate-sources

unpack





com.test

assembly

1.0.1

zip

true

${target.basedir}







These dependencies should also be included in the final artifact.jar
file. But after I have run mvn clean install the artifact.jar file
only contains the manifest file.

How do I include resources from the project and target folder i the
final artifact.jar file?

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

Re: Parent Dependencies

[Kiren Pillay]

I see I've misinterpreted the concept from the maven guide. Thanks for
clearing up my misunderstanding!  :)

Best regards
Kiren

On Fri, Sep 30, 2011 at 1:53 PM, Guillaume Polet
 wrote:
> Hi,
>
> So I have briefly read your pom.xml and it seems that you have put the
> dependency for spring in the dependencyMgmt element and not in the
> dependencies element. So let me straight things out here:
> * dependencyMgmt are used to declare version number, configuration, scope,
> etc... but it does not mean that you depend on them, you just inform Maven
> of the default values to use, if they are not defined in the dependencies
> element.
> * dependencies are used to declare on which artifacts your project(s)
> depend. If you do not define version, scope, etc..., Maven will try to pick
> them up from the dependencyMgmt.
>
> A best practice is to define in your super pom, the version of all your
> dependencies of all your project in the dependencyMgmt and then simply
> "instantiate" those dependency in each child project. This allows you to
> centralize all the versions of all jars used in all projects.
>
> So in your super pom you define:
> 
> 
> x.y.z
> azerty
> 1.2.3
> 
>    ...
> 
>
> Then in your child pom you can simply put:
> 
> 
> x.y.z
> azerty
> 
>    ...
> 
> without the version number, and Maven will automatically find that you want
> version 1.2.3. Yet, you can still "override" this default value by setting
> the version number in the child pom.
>
> In the dependency
>
> Le 30/09/2011 11:02, Kiren Pillay a écrit :
>>
>> Hi
>>
>> I think our project is misconfigured. From reading the docs again, the
>> common dependencies go to within the dependencyManagent tag (we where
>> using the dependencies before).
>>
>> I've fixed this but still see that the dependencies declared in the
>> super pom aren't being picked up by the children.
>>
>> For instance the springframeork annotation package isn't being picked
>> up even though its in the super pom.
>>
>> [ERROR]
>> /home/kiren/Documents/workspace-subsnp/pams-main/core/advantage/src/main/java/za/co/vodacom/pams/core/in/dao/INSubscriberProfileDaoImpl.java:[4,51]
>> package org.springframework.beans.factory.annotation does not exist
>>
>> Child:
>>
>> 
>>
>> 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
>>
>>     
>>         za.co.vodacom.pams
>>         pams-core
>>         1.2.1-DEV-SNAPSHOT
>>     
>>
>>     za.co.vodacom.pams
>>     pams-advantage
>>     1.2.1-DEV-SNAPSHOT
>>     PAMS Core - IN DAO
>>     jar
>>
>>   
>>
>>         
>>         
>>             za.co.vodacom.advantage
>>             advantage-corba-interface
>>         
>>
>>          
>>             za.co.vodacom.fap
>>             fap-core
>>             ${fcaps.version}
>>                jar
>>                compile
>>         
>>
>>
>>   
>>
>>     
>>         
>>             
>>                 maven-compiler-plugin
>>                 
>>                     ${java.source.version}
>>                     ${java.target.version}
>>                     true
>>                 
>>             
>>             
>>                 maven-surefire-plugin
>>                 
>>                     never
>>                 
>>             
>>         
>>     
>>
>> 
>>
>>
>>
>>
>> Parent:
>>
>> 
>>
>> 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
>>
>>     
>>         za.co.vodacom.pams
>>         pams-main
>>         1.2.1-DEV-SNAPSHOT
>>     
>>
>>     za.co.vodacom.pams
>>     pams-core
>>     PAMS Core
>>     pom
>>     1.2.1-DEV-SNAPSHOT
>>
>>     
>> 
>>         common
>>         pams-schema
>>         advantage
>>         ppfe-connectors
>>         ppfe_dao
>>         pams-rms-dao
>>         pams-pams-dao
>>        
>>         pams-cur-dao
>>     
>>
>> 
>>
>> Super ("Grandparent")
>>
>> 
>>
>> 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
>>
>>     za.co.vodacom.pams
>>     pams-main
>>     1.2.1-DEV-SNAPSHOT
>>     pom
>>     PAMS - Main
>>
>>     
>>         core
>>         business_services
>>     
>>
>>     
>>         1.2.1-DEV-SNAPSHOT
>>         1.1.0
>>         3.0.5.RELEASE
>>         1.6.1
>>
>>         1.2.16
>>         4.8.1
>>         1.6
>>         1.6
>>
>>         2.4.2
>>         3.1
>>         1.1.1
>>         2.5.0
>>         8.9.26
>>         3.3.2.GA
>>         1.6.1
>>         slf4j-log4j12
>>         1.2.2
>>         5.64
>>
>>     
>>     
>>        
>>         
>>
>>             
>>                 maven-jar-plugin
>>          

Re: [m2e-users] maven 3.0.3 - performance with version ranges

[Paul French]

wow!

Dropped in aether 1.13 into apache maven lib/ext (so patched applied 
external to eclipse) and also updated the m2e embedded runtime plugin 
org.eclipse.m2e.maven.runtime_1.0.1.201106291304  (as a quick test) and 
now as an example a build that took 1 minute 43 secs now only takes 5 
seconds.


Will build our own embedded runtime as instructed below now.

Thanks for everyone's help.

Any ideas when an official maven 3.0.4 release will happen as well as an 
official maven 3.0.4 embedded runtime m2e connector ?


Paul French
Kirona Solutions Ltd
Tel: 07803 122 058
E-Mail: paul.fre...@kirona.com
Web: www.kirona.com 

This email and any attachments are confidential and should only be read 
by those to whom they are addressed. If you are not the intended 
recipient, please contact us on 01625 585511, delete the email 
(including any attachment) from your computer and destroy any copies. 
Any distribution or copying without our prior permission is prohibited. 
Internet communications are not always secure and may be subject to 
delays, non-delivery and unauthorised alterations. Therefore, 
information expressed in this message is not given or endorsed by Kirona 
Solutions Limited ("Kirona") unless otherwise notified by our duly 
authorised representative independent of this message. No warranty is 
given that this email (including any attachment) is virus free. Any 
views or opinions presented are solely those of the author and do not 
necessarily represent those of Kirona.


Registered addresses: Kirona Solutions Limited, Barrington House, Heyes 
Lane, Alderley Edge, Cheshire. SK9 7LA Registered in England and Wales 
No: 04678711



On 30/09/2011 12:28, Igor Fedorenko wrote:

I do not know if the underlying problem has been solved with aether
and/or maven. You need to talk to aether and/or maven developers to find
out.

As far updating m2e embedded maven runtime, it is relatively easy now --
setup development environment as explain in [1], then change
m2e-maven-runtime/org.eclipse.m2e.maven.runtime/pom.xml to use whatever
version of dependencies you want to try.

[1] http://wiki.eclipse.org/M2E_Development_Environment

--
Regards,
Igor

On 11-09-30 6:22 AM, Paul French wrote:

maven 3.0.3 has terrible performance and memory usage when using version
ranges. This has a knock on effect using m2e

It takes maven ages to update the maven dependencies.

I have a main project with a some version ranged dependencies which in
turn have versioned ranged dependencies. Outside of eclipse it takes
many minutes and considerable memory to get a successful build. Most
time is spent resolving the dependencies.

I have also run maven offline when I know I have all dependencies in my
local repo and it is still very, very slow.

In m2e (and workspace resolution on), you can check out a dependency
that is very simple and this triggers a re-build of the main project.
The same happens when you delete the dependent project or make pom
version changes to it. So in eclipse this becomes really tedious
especially if you have 4 or 5 related projects checked out. You end up
sitting and waiting for your workspace to be re-built all the time.

I understand what maven is doing but I do believe it could be done a lot
better when resolving version ranges.

I also know maven 3.0.3 uses aether 1.11 to so its dependency 
management.


I'm really keen to try and find a solution. aether 1.12 has been
released. Is there anyway I can hook this into maven 3.0.3

Does aether 1.12 solve

Is there a pre-release of maven 3.0.4 out there yet that I can try and
does it use aether 1.12 ?

Thanks
Paul

___
m2e-users mailing list
m2e-us...@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users

___
m2e-users mailing list
m2e-us...@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users

Re: Parent Dependencies

[Guillaume Polet]

Hi,

So I have briefly read your pom.xml and it seems that you have put the 
dependency for spring in the dependencyMgmt element and not in the 
dependencies element. So let me straight things out here:
* dependencyMgmt are used to declare version number, configuration, 
scope, etc... but it does not mean that you depend on them, you just 
inform Maven of the default values to use, if they are not defined in 
the dependencies element.
* dependencies are used to declare on which artifacts your project(s) 
depend. If you do not define version, scope, etc..., Maven will try to 
pick them up from the dependencyMgmt.


A best practice is to define in your super pom, the version of all your 
dependencies of all your project in the dependencyMgmt and then simply 
"instantiate" those dependency in each child project. This allows you to 
centralize all the versions of all jars used in all projects.


So in your super pom you define:


x.y.z
azerty
1.2.3

...


Then in your child pom you can simply put:


x.y.z
azerty

...

without the version number, and Maven will automatically find that you 
want version 1.2.3. Yet, you can still "override" this default value by 
setting the version number in the child pom.


In the dependency

Le 30/09/2011 11:02, Kiren Pillay a écrit :

Hi

I think our project is misconfigured. From reading the docs again, the
common dependencies go to within the dependencyManagent tag (we where
using the dependencies before).

I've fixed this but still see that the dependencies declared in the
super pom aren't being picked up by the children.

For instance the springframeork annotation package isn't being picked
up even though its in the super pom.

[ERROR] 
/home/kiren/Documents/workspace-subsnp/pams-main/core/advantage/src/main/java/za/co/vodacom/pams/core/in/dao/INSubscriberProfileDaoImpl.java:[4,51]
package org.springframework.beans.factory.annotation does not exist

Child:



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

 
 za.co.vodacom.pams
 pams-core
 1.2.1-DEV-SNAPSHOT
 

 za.co.vodacom.pams
 pams-advantage
 1.2.1-DEV-SNAPSHOT
 PAMS Core - IN DAO
 jar

   

 
 
 za.co.vodacom.advantage
 advantage-corba-interface
 

  
 za.co.vodacom.fap
 fap-core
 ${fcaps.version}
jar
compile
 


   

 
 
 
 maven-compiler-plugin
 
 ${java.source.version}
 ${java.target.version}
 true
 
 
 
 maven-surefire-plugin
 
 never
 
 
 
 






Parent:



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

 
 za.co.vodacom.pams
 pams-main
 1.2.1-DEV-SNAPSHOT
 

 za.co.vodacom.pams
 pams-core
 PAMS Core
 pom
 1.2.1-DEV-SNAPSHOT

 

 common
 pams-schema
 advantage
 ppfe-connectors
 ppfe_dao
 pams-rms-dao
 pams-pams-dao

 pams-cur-dao
 



Super ("Grandparent")



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

 za.co.vodacom.pams
 pams-main
 1.2.1-DEV-SNAPSHOT
 pom
 PAMS - Main

 
 core
 business_services
 

 
 1.2.1-DEV-SNAPSHOT
 1.1.0
 3.0.5.RELEASE
 1.6.1

 1.2.16
 4.8.1
 1.6
 1.6

 2.4.2
 3.1
 1.1.1
 2.5.0
 8.9.26
 3.3.2.GA
 1.6.1
 slf4j-log4j12
 1.2.2
 5.64

 
 

 

 
 maven-jar-plugin
 2.3.1
 
 
 
 test-jar
 
 test-compile
 

 

 

 
 

  
  
 
 org.springframework
 spring-test
 ${spring.version}
 

 

 

 

 
za.co.vodacom.pams
pams-core-xsd-server
${pams.version}
jar
com

RE: maven 3.0.3 - performance with version ranges

[Thiebaud, Christophe]

FYI, You can tell maven 3.0.3 to work with aether 1.13 (I think this is the 
latest release) just by dropping aether jars in $MAVEN_HOME/lib/ext. They 
should take precedence over the aether 1.11 bundled with maven in 
$MAVEN_HOME/lib.
I did that with aether 1.12 and there was no issue, at least for my projects.
Christophe


-Original Message-
From: Paul French [mailto:paul.fre...@kirona.com] 
Sent: Freitag, 30. September 2011 12:22
To: Maven Users List; Maven Integration for Eclipse users mailing list
Subject: maven 3.0.3 - performance with version ranges

maven 3.0.3 has terrible performance and memory usage when using version 
ranges. This has a knock on effect using m2e

It takes maven ages to update the maven dependencies.

I have a main project with a some version ranged dependencies which in 
turn have versioned ranged dependencies. Outside of eclipse it takes 
many minutes and considerable memory to get a successful build. Most 
time is spent resolving the dependencies.

I have also run maven offline when I know I have all dependencies in my 
local repo and it is still very, very slow.

In m2e (and workspace resolution on), you can check out a dependency 
that is very simple and this triggers a re-build of the main project. 
The same happens when you delete the dependent project or make pom 
version changes to it. So in eclipse this becomes really tedious 
especially if you have 4 or 5 related projects checked out. You end up 
sitting and waiting for your workspace to be re-built all the time.

I understand what maven is doing but I do believe it could be done a lot 
better when resolving version ranges.

I also know maven 3.0.3 uses aether 1.11 to so its dependency management.

I'm really keen to try and find a solution. aether 1.12 has been 
released. Is there anyway I can hook this into maven 3.0.3

Does aether 1.12 solve

Is there a pre-release of maven 3.0.4 out there yet that I can try and 
does it use aether 1.12 ?

Thanks
Paul


-
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: maven 3.0.3 - performance with version ranges

[Tamás Cservenák]

Take a peek at this thread (especially 1st mail):
http://maven.40175.n5.nabble.com/Apache-Maven-distribution-with-fixes-td4639045.html

Thanks,
~t~

On Fri, Sep 30, 2011 at 12:22 PM, Paul French  wrote:
> maven 3.0.3 has terrible performance and memory usage when using version
> ranges. This has a knock on effect using m2e
>
> It takes maven ages to update the maven dependencies.
>
> I have a main project with a some version ranged dependencies which in turn
> have versioned ranged dependencies. Outside of eclipse it takes many minutes
> and considerable memory to get a successful build. Most time is spent
> resolving the dependencies.
>
> I have also run maven offline when I know I have all dependencies in my
> local repo and it is still very, very slow.
>
> In m2e (and workspace resolution on), you can check out a dependency that is
> very simple and this triggers a re-build of the main project. The same
> happens when you delete the dependent project or make pom version changes to
> it. So in eclipse this becomes really tedious especially if you have 4 or 5
> related projects checked out. You end up sitting and waiting for your
> workspace to be re-built all the time.
>
> I understand what maven is doing but I do believe it could be done a lot
> better when resolving version ranges.
>
> I also know maven 3.0.3 uses aether 1.11 to so its dependency management.
>
> I'm really keen to try and find a solution. aether 1.12 has been released.
> Is there anyway I can hook this into maven 3.0.3
>
> Does aether 1.12 solve
>
> Is there a pre-release of maven 3.0.4 out there yet that I can try and does
> it use aether 1.12 ?
>
> Thanks
> Paul
>
>
> -
> 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

maven 3.0.3 - performance with version ranges

[Paul French]

maven 3.0.3 has terrible performance and memory usage when using version 
ranges. This has a knock on effect using m2e


It takes maven ages to update the maven dependencies.

I have a main project with a some version ranged dependencies which in 
turn have versioned ranged dependencies. Outside of eclipse it takes 
many minutes and considerable memory to get a successful build. Most 
time is spent resolving the dependencies.


I have also run maven offline when I know I have all dependencies in my 
local repo and it is still very, very slow.


In m2e (and workspace resolution on), you can check out a dependency 
that is very simple and this triggers a re-build of the main project. 
The same happens when you delete the dependent project or make pom 
version changes to it. So in eclipse this becomes really tedious 
especially if you have 4 or 5 related projects checked out. You end up 
sitting and waiting for your workspace to be re-built all the time.


I understand what maven is doing but I do believe it could be done a lot 
better when resolving version ranges.


I also know maven 3.0.3 uses aether 1.11 to so its dependency management.

I'm really keen to try and find a solution. aether 1.12 has been 
released. Is there anyway I can hook this into maven 3.0.3


Does aether 1.12 solve

Is there a pre-release of maven 3.0.4 out there yet that I can try and 
does it use aether 1.12 ?


Thanks
Paul


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

Re: Parent Dependencies

[Kiren Pillay]

Hi

I think our project is misconfigured. From reading the docs again, the
common dependencies go to within the dependencyManagent tag (we where
using the dependencies before).

I've fixed this but still see that the dependencies declared in the
super pom aren't being picked up by the children.

For instance the springframeork annotation package isn't being picked
up even though its in the super pom.

[ERROR] 
/home/kiren/Documents/workspace-subsnp/pams-main/core/advantage/src/main/java/za/co/vodacom/pams/core/in/dao/INSubscriberProfileDaoImpl.java:[4,51]
package org.springframework.beans.factory.annotation does not exist

Child:



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


za.co.vodacom.pams
pams-core
1.2.1-DEV-SNAPSHOT


za.co.vodacom.pams
pams-advantage
1.2.1-DEV-SNAPSHOT
PAMS Core - IN DAO
jar

  



za.co.vodacom.advantage
advantage-corba-interface


 
za.co.vodacom.fap
fap-core
${fcaps.version}
jar
compile



  




maven-compiler-plugin

${java.source.version}
${java.target.version}
true



maven-surefire-plugin

never










Parent:



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


za.co.vodacom.pams
pams-main
1.2.1-DEV-SNAPSHOT


za.co.vodacom.pams
pams-core
PAMS Core
pom
1.2.1-DEV-SNAPSHOT



common
pams-schema
advantage
ppfe-connectors
ppfe_dao
pams-rms-dao
pams-pams-dao
   
pams-cur-dao




Super ("Grandparent")



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

za.co.vodacom.pams
pams-main
1.2.1-DEV-SNAPSHOT
pom
PAMS - Main


core
business_services



1.2.1-DEV-SNAPSHOT
1.1.0
3.0.5.RELEASE
1.6.1

1.2.16
4.8.1
1.6
1.6

2.4.2
3.1
1.1.1
2.5.0
8.9.26
3.3.2.GA
1.6.1
slf4j-log4j12
1.2.2
5.64



   



maven-jar-plugin
2.3.1



test-jar

test-compile









 
 

org.springframework
spring-test
${spring.version}

   







za.co.vodacom.pams
pams-core-xsd-server
${pams.version}
jar
compile



org.slf4j
slf4j-api
${slf4j.version}
jar



org.slf4j
jcl-over-slf4j
${slf4j.version}
jar



org.slf4j
${slf4j.log4j.version}
${slf4j.version}
jar




com.tandem.t4jdbc
t4sqlmx
${tandem.jdbc.version}
jar


commons-logging
commons-logging







org.hibernate
hibernate-core
${hibernate.version}
jar


commons-logging
commons-logging




org.hibernate
hibernate-entitymanager
${hibernate.version}
jar


cglib
cglib


   

Maven site gives plugin X does not exist or no valid version could be found

[Bram Patelski]

Hi,

I am using Jenkins on a buildserver that runs all builds every night at
about 0:00.
I also have builds on those projects that run the site-plugin.
But each night, a lot of those builds fail on some random plugin, logging
the following error:


[ERROR] BUILD ERROR


[INFO] 
[INFO] The plugin 'org.codehaus.mojo:taglist-maven-plugin' does not
exist or no valid version could be found


The listed plugin can be any one plugin, which can be different every time.
If I manually delete the plugin that caused the error, then run all
site-builds again,
everything is fine, but the next nightly-build fails again on another
plugin.

Help!
Can someone help me have nightly site-builds run smoothly, without these
errors?

Thanks,
Bram

Re: Using Maven with custom libraries which are not in repository.

[Anders Hammar]

I suggest using http://search.maven.org instead as that's the official
search engine for Maven central, which is the default repo for Maven.

/Anders

On Thu, Sep 29, 2011 at 08:47, Yuvaraj Vanarase
 wrote:
> Prashant,
>
> If those libraries are standard and well known then should be available at 
> some maven repository. You can try http://mvnrepository.com to find it out.
> Generally, you should setup your own repository may be using artifactory and 
> put all dependencies there. Requirement is maven should able to access those 
> jars while build, once artifact is ready it will contain required jars, thus 
> complete deployable.
>
> Hope this helps!
>
> Regards,
> Yuvaraj
>
> Yuvaraj Vanarase,
> Lead Technology - Software
> Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 
> | http://www.synechron.com
> SYNECHRON -
> - Top 10 Best IT Employers for 4 consecutive years (link).
> - Celebrating 10 Years!
>
> -Original Message-
> From: Prashant Neginahal [mailto:prashu.n...@gmail.com]
> Sent: Thursday, September 29, 2011 12:14 PM
> To: Maven Users List
> Subject: Using Maven with custom libraries which are not in repository.
>
> Hi All,
>
> We are starting new web project. But, it has to be built on some proprietary
> web framework which is NOT mavenised and comes with its own bunch
> of libraries. I am thinking of using maven for this application development.
> But, just wondering how to ensure maven uses this proprietary framework and
> its libraries which are not there in repository. Can we just dump framework
> libraries in WEB_INF/lib folder and maven includes the same in its
> CLASSPATH.
>
> Thanks,
> Prashant
>
> -
> 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: customisation of path in pom

[sandy]

thank you for the reply

could you please let me know bit clearly..because i am very new to maven

--
View this message in context: 
http://maven.40175.n5.nabble.com/customisation-of-path-in-pom-tp4853264p4856085.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: customisation of path in pom

[sandy]

Thank you for the reply.

How can i differentiate this with different os..

I mean I run the tests on my local machine with windows os
and my test system is with linux...

thank you

--
View this message in context: 
http://maven.40175.n5.nabble.com/customisation-of-path-in-pom-tp4853264p4856081.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: Build hangs on maven site generation

[Bram Patelski]

Hi,

I've replied several times to an old thread, but never got my mail accepted
by the list.
It concerns this thread:
http://jenkins.361315.n4.nabble.com/Build-hangs-on-maven-site-generation-td366706.html

My post:
Hi,

I have these same problems, but not on all projects/builds. As with the
original issue: mvn clean package works like a charm, but mvn clean
site-deploy does not from Jenkins. I tried to call Maven from commandline
and that works fine. Also: most site-deploy tasks in Jenkins work after I
run it once from commandline, then re-trigger the task manually.
I compared the poms of different projects (one that works compared to one
that doesn't), but can't see any differences.

Can I check anything else to find out what's causing this?

Working on:
- Windows
- Jenkins 1.405 (deployed as WAR on Apache Tomcat 6.0)
- Jenkins Subversion Plug-in 1.26

Some more testing:
If I run from command-line first, I can run the Jenkins task successful only
once. If I run the Jenkins task again, it hangs:

[INFO] SCM Command Line[0]: svn
[INFO] SCM Command Line[1]: log
[INFO] SCM Command Line[2]: -v
[INFO] SCM Command Line[3]: "-r{2011-05-18}:{2011-04-17}"

Thanks