Re: What is the different between using ant tasks and antrun plugin?

[Wayne Fay]

Use ant-tasks if you want to integrate certain Maven functions into
your ant build.xml scripts. This is for people who want to keep using
Ant as their primary build tool. I don't think you want to do this.

Use antrun plugin if you want to call ant tasks from your Maven build.
This is for people who are trying to use Maven as their primary build
tool. I think this is what you're trying to do.

Wayne

On 2/1/08, Baz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am trying to execute some existing ant build.xml files with maven 2. I am
> confuse if i should use antrun plugin (
> http://maven.apache.org/plugins/maven-antrun-plugin/) or ant tasks (
> http://maven.apache.org/ant-tasks.html)
>
> Can someone help to explain?
>
> Thanks.
>
> A.
>

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

Re: site generation links modules in staging but uses wrong link when deploy

[simon]

On Thu, 2008-01-31 at 16:28 -0700, Brice Lambi wrote:
> Hello,
> 
> I have a project with sub-projects.  When I run 'mvn site-deploy' it will
> deploy the project but the "modules" links on the left link to
> http://maven.apache.org.  When I do 'mvn site:stage' it works as expected
> and the "modules" links properly link to the corresponding sub-directory.
> Has anyone else had this problem?

I've had endless pain with site links :-(

Make sure that the project  tag in the pom is correct; that has a
major impact on what links are generated by the site plugin.

Regards, Simon


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

Re: maven renaming jar files

[amit kumar]

Actually all that happened ( installing commons into the LAN
repository ) on the second day of i started using maven(2nd week of my
first job :) ), there has been a strict deadline for that. But anyways
I guess these are just lame excuses for misusing maven(unintentional),
but at that time thats' what I thought it is like(which could be
wrong). And my experience with groupId's has always been confusing, at
places it is the package name while others artifactId and groupId
becomes the same. That amplified the motivation to commit the mistake,
and there are few commons artifacts being used here at my workplace
which are not there in the repo1.maven.org ( i.e.
commons-email-1.0-mod.jar).

But I believe everyone learns with time, and learning is best when it
comes from the mistakes you commit.

Thanks for the help.

Regards,
Amit

On Jan 31, 2008 1:57 PM, Stephen Connolly
<[EMAIL PROTECTED]> wrote:
> Or if you are checking them in manually, at least use a different version
> which includes your company name, e.g.
>
> commons-logging
> commins-logging
> 1.0-mycompany-1
>
> That way maven will at least detect that these are different versions of the
> same artifact and the version ranges and preferences should* let you pick
> your one!
>
> -Stephen
>
> * Yes I know some people have issues with version ranges, etc. but there are
> ways of making them work, or at least using a dependencyManagement section
>
>
> On Jan 31, 2008 4:07 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> > We've had more than one person show up on this list complaining about
> > strange difficulties with Maven. After a bit of prodding, they tell us
> > that they manually created their repo and the pom files, if they exist
> > at all, are just GAV with no transitive deps. And then they're usually
> > complaining about how Maven isn't working like they expected.
> >
> > I just want to make sure this happens to as few people as possible. If
> > you know what you're doing and want to check-in some files, please do
> > it, especially for things like Websphere and Weblogic that will never
> > appear in the Central repo.
> >
> > But doing this for things like commons-* is a bad practice. Even if
> > you know what you're doing, you probably should not be checking in
> > files like these manually.
> >
> > Wayne
> >
> > On 1/31/08, Simon Kitching <[EMAIL PROTECTED]> wrote:
> > > I've certainly done something similar in the past. To reduce network
> > traffic, and to better control what libs are used, it is nice to have a
> > repository on a local server hosting the jars you need.
> > >
> > > It is very tempting to just take the set of jars you have always been
> > using (in an existing ant-based build process or similar) and just upload
> > them to that new repository. It is certainly easier than finding a maven
> > repository proxy application, and setting that up.
> > >
> > > I don't see a lot wrong with doing that - except that you do need to get
> > the group ids right!
> > >
> > > Of course long-term, having a proper repository manager installed
> > locally appears to be the right solution. Some day I have to get that
> > organised for my workplace...
> > >
> > > Interesting to see that the war plugin does detect filename clashes; as
> > discussed in another thread recently it appears that the dependency plugin
> > does not...
> > >
> > > Regards,
> > > Simon
> > >
> > >  Wayne Fay <[EMAIL PROTECTED]> schrieb:
> > > > If you're using "mvn install" or "mvn deploy" to install/deploy common
> > > > artifacts like commons-logging etc, then you're probably using Maven
> > > > wrong.
> > > >
> > > > What you've described is exactly what the problem was. You had added
> > > > c-l as a particular G/A/V and then c-l was coming in as a transitive
> > > > dep under a different G/A/V. Since the plugin detected a name
> > > > collision, it expanded the name to include the group as well, to make
> > > > it unique.
> > > >
> > > > Why did you install/deploy commons-logging instead of simply adding a
> > > > ? You're not the first person to report doing this, so I
> > > > want to understand if there is a failure in the documentation
> > > > somewhere or if new users are simply making poor assumptions about
> > > > what Maven does.
> > > >
> > > > Wayne
> > > >
> > > > On 1/31/08, amit kumar <[EMAIL PROTECTED]> wrote:
> > > > > I have overcome the problem. And guess know the reason for that,
> > > > > actually at the time of creating the LAN maven repository, I have
> > > > > installed common components under org.apache.commons groupId (
> > > > > assuming the convention of groupId as package name ). So now when I
> > > > > was including commons-logging as dependency in my pom.xml,
> > > > > what I added to pom looked like
> > > > >
> > > > > org.apache.commons
> > > > > commons-logging
> > > > > 1.1
> > > > >
> > > > > But there was another dependency in my pom.xml which as
> > > > > commons-logging as transitive dependency with same version, so what
> > > > >

What is the different between using ant tasks and antrun plugin?

[Baz]

Hi,

I am trying to execute some existing ant build.xml files with maven 2. I am
confuse if i should use antrun plugin (
http://maven.apache.org/plugins/maven-antrun-plugin/) or ant tasks (
http://maven.apache.org/ant-tasks.html)

Can someone help to explain?

Thanks.

A.

Re: FW: surefire and initial context

[Brice Lambi]

You can put a sleep statement in your test so that you can pause the process
long enough to run ps and see the java command being executed.  That output
will have the full classpath the jvm is getting.  You could then compare the
output from eclipse and maven.  Or just use 'jar tvf' to find which jar file
that class is in and make sure you find it in the corresponding artifact in
your local repository.

Also make sure you don't have a scope on one of those dependencies that
would cause it to not show up in tests.  Eclipse and maven might handle
scopes differently.



On Jan 31, 2008 5:49 PM, Matthew Shaw <[EMAIL PROTECTED]> wrote:

> Thought I'd try again with this one. I am totally stuck. Any help would
> be greatly appreciated.
>
> -Original Message-
> From: Matthew Shaw [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 31 January 2008 1:53 PM
> To: users@maven.apache.org
> Subject: surefire and initial context
>
> Hi there,
>
>
>
> I am running maven2 and surefire plugin 2.4 to execute junit4 style
> tests.
>
>
>
> I am using spring2.5 and creating a jndiTemplate bean with the following
> properties to talk to a weblogic 10 server message queue.
>
> 
>
>  
>
>  
>
>  
>
>weblogic.jndi.WLInitialContextFactory
>
>  
>
>  
>
>t3://localhost:7001
>
>  
>
>  
>
>  
>
>  
>
>
>
> When I run my test using eclipse it creates the bean no problem. If I
> try to run it using maven I get the following trace:
>
>
>
> Caused by: java.lang.NoClassDefFoundError:
> weblogic/jndi/spi/EnvironmentManager
>
>  at weblogic.jndi.Environment.getContext(Environment.java:307)
>
>  at weblogic.jndi.Environment.getContext(Environment.java:277)
>
>  at
> weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContext
> Factory.java:117)
>
>  at
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
>
>  at
> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
>
>  at javax.naming.InitialContext.init(InitialContext.java:223)
>
>  at javax.naming.InitialContext.(InitialContext.java:197)
>
>  at
> org.springframework.jndi.JndiTemplate.createInitialContext(JndiTemplate.
> java:105)
>
>  at
> org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:83)
>
>  at
> org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:121)
>
>  at
> org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:146)
>
>  at
> org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.ja
> va:93)
>
>  at
> org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java
> :105)
>
>  at
> org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiOb
> jectFactoryBean.java:197)
>
>  at
> org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiOb
> jectFactoryBean.java:184)
>
>  at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1390)
>
>  at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.initializeBean(AbstractAutowireCapableBeanFactory.java:1359)
>
>
>
> I am including the following dependencies for weblogic:
>
> 
>
>  weblogic-server
>
>  api
>
>  10.0.0.0
>
>
>
>
>
>  weblogic-server
>
>  wls-api
>
>  10.0.0.0
>
>
>
>
>
>  weblogic-server
>
>  wlclient
>
>  10.0.0.0
>
>
>
>
>
>  weblogic-server
>
>  wljmsclient
>
>  10.0.0.0
>
>
>
>
>
> Has anyone come across a similar issue? I can only assume it is a
> problem with the surefire plugin as it works fine in eclipse and the
> eclipse classpath is being built from my maven dependencies.
>
>
>
> I am stumped on this.
>
>
>
> Cheers,
>
> Matt.
>
> 
>
> This email and associated attachments may contain confidential and
> privileged CITEC information that is provided solely for the use of the
> intended addressee. Views and opinions expressed in this email are those
> of the individual sender and are not necessarily the views and opinions
> of CITEC unless the sender expressly states that such views and opinions
> are those of CITEC. The privilege and confidentiality associated with
> this email and attachments will not be waived, lost or rescinded by
> reason of mistaken delivery. Should you receive this email by mistake,
> please notify the sender by return email then delete the email from your
> computer system. You must not use, copy, modify, print, or distribute
> the email or the information and attachments contained within same to
> any third party. CITEC does not accept any liability in respect of
> viruses or computer problems experienced by the recipient through access
> gained to this email and its attachments.
> 

Re: FW: surefire and initial context

[Wayne Fay]

Eclipse sometimes does "stuff" for users that makes things work when
they really "shouldn't". Can you try running from the command line
without using Maven by calling java directly or perhaps using Ant? I
believe it won't work either - you're probably doing something just
slightly wrong.

Also, open up those JAR files (I guess you installed them into your
local repo cache?) and make sure the class
weblogic/jndi/spi/EnvironmentManager exists in one of them.

Wayne

On 1/31/08, Matthew Shaw <[EMAIL PROTECTED]> wrote:
> Thought I'd try again with this one. I am totally stuck. Any help would
> be greatly appreciated.
>
> -Original Message-
> From: Matthew Shaw [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 31 January 2008 1:53 PM
> To: users@maven.apache.org
> Subject: surefire and initial context
>
> Hi there,
>
>
>
> I am running maven2 and surefire plugin 2.4 to execute junit4 style
> tests.
>
>
>
> I am using spring2.5 and creating a jndiTemplate bean with the following
> properties to talk to a weblogic 10 server message queue.
>
> 
>
>  
>
>  
>
>  
>
>weblogic.jndi.WLInitialContextFactory
>
>  
>
>  
>
>t3://localhost:7001
>
>  
>
>  
>
>  
>
>  
>
>
>
> When I run my test using eclipse it creates the bean no problem. If I
> try to run it using maven I get the following trace:
>
>
>
> Caused by: java.lang.NoClassDefFoundError:
> weblogic/jndi/spi/EnvironmentManager
>
>  at weblogic.jndi.Environment.getContext(Environment.java:307)
>
>  at weblogic.jndi.Environment.getContext(Environment.java:277)
>
>  at
> weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContext
> Factory.java:117)
>
>  at
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
>
>  at
> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
>
>  at javax.naming.InitialContext.init(InitialContext.java:223)
>
>  at javax.naming.InitialContext.(InitialContext.java:197)
>
>  at
> org.springframework.jndi.JndiTemplate.createInitialContext(JndiTemplate.
> java:105)
>
>  at
> org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:83)
>
>  at
> org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:121)
>
>  at
> org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:146)
>
>  at
> org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.ja
> va:93)
>
>  at
> org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java
> :105)
>
>  at
> org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiOb
> jectFactoryBean.java:197)
>
>  at
> org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiOb
> jectFactoryBean.java:184)
>
>  at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1390)
>
>  at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.initializeBean(AbstractAutowireCapableBeanFactory.java:1359)
>
>
>
> I am including the following dependencies for weblogic:
>
> 
>
>  weblogic-server
>
>  api
>
>  10.0.0.0
>
>
>
>
>
>  weblogic-server
>
>  wls-api
>
>  10.0.0.0
>
>
>
>
>
>  weblogic-server
>
>  wlclient
>
>  10.0.0.0
>
>
>
>
>
>  weblogic-server
>
>  wljmsclient
>
>  10.0.0.0
>
>
>
>
>
> Has anyone come across a similar issue? I can only assume it is a
> problem with the surefire plugin as it works fine in eclipse and the
> eclipse classpath is being built from my maven dependencies.
>
>
>
> I am stumped on this.
>
>
>
> Cheers,
>
> Matt.
>
> 
>
> This email and associated attachments may contain confidential and
> privileged CITEC information that is provided solely for the use of the
> intended addressee. Views and opinions expressed in this email are those
> of the individual sender and are not necessarily the views and opinions
> of CITEC unless the sender expressly states that such views and opinions
> are those of CITEC. The privilege and confidentiality associated with
> this email and attachments will not be waived, lost or rescinded by
> reason of mistaken delivery. Should you receive this email by mistake,
> please notify the sender by return email then delete the email from your
> computer system. You must not use, copy, modify, print, or distribute
> the email or the information and attachments contained within same to
> any third party. CITEC does not accept any liability in respect of
> viruses or computer problems experienced by the recipient through access
> gained to this email and its attachments.
> 
> 

How to adjust the screen size of the output

[Tawfik, Sameh E]

After the build is complete, when I click on Build History icon followed
by clicking on the Result icon, the output screen is too big! The output
screen is behind Continuum main screen, and the output screen is much
bigger in size than Continuum screen, so its scroll bars are hidden
behind Continuum screen, and I've to do lots of scrolling to the right
and to the bottom of Continuum screen to be able to reach the output
screen scroll bars so I can view the output! It is very cumbersome to
view the results.

Is there is a way to adjust the size of the output screen so it would
fit inside the parent Continuum screen, so it would be easy to scroll
and view?


This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.

FW: surefire and initial context

[Matthew Shaw]

Thought I'd try again with this one. I am totally stuck. Any help would
be greatly appreciated.

-Original Message-
From: Matthew Shaw [mailto:[EMAIL PROTECTED] 
Sent: Thursday, 31 January 2008 1:53 PM
To: users@maven.apache.org
Subject: surefire and initial context

Hi there,

 

I am running maven2 and surefire plugin 2.4 to execute junit4 style
tests. 

 

I am using spring2.5 and creating a jndiTemplate bean with the following
properties to talk to a weblogic 10 server message queue.



  

  

  

weblogic.jndi.WLInitialContextFactory

  

  

t3://localhost:7001

  

  

  

  

 

When I run my test using eclipse it creates the bean no problem. If I
try to run it using maven I get the following trace:

 

Caused by: java.lang.NoClassDefFoundError:
weblogic/jndi/spi/EnvironmentManager

  at weblogic.jndi.Environment.getContext(Environment.java:307)

  at weblogic.jndi.Environment.getContext(Environment.java:277)

  at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContext
Factory.java:117)

  at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

  at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)

  at javax.naming.InitialContext.init(InitialContext.java:223)

  at javax.naming.InitialContext.(InitialContext.java:197)

  at
org.springframework.jndi.JndiTemplate.createInitialContext(JndiTemplate.
java:105)

  at
org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:83)

  at
org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:121)

  at
org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:146)

  at
org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.ja
va:93)

  at
org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java
:105)

  at
org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiOb
jectFactoryBean.java:197)

  at
org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiOb
jectFactoryBean.java:184)

  at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
tory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1390)

  at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
tory.initializeBean(AbstractAutowireCapableBeanFactory.java:1359)

 

I am including the following dependencies for weblogic:



  weblogic-server

  api

  10.0.0.0





  weblogic-server

  wls-api

  10.0.0.0





  weblogic-server

  wlclient

  10.0.0.0





  weblogic-server

  wljmsclient

  10.0.0.0



 

Has anyone come across a similar issue? I can only assume it is a
problem with the surefire plugin as it works fine in eclipse and the
eclipse classpath is being built from my maven dependencies.

 

I am stumped on this.

 

Cheers,

Matt.
 


This email and associated attachments may contain confidential and
privileged CITEC information that is provided solely for the use of the
intended addressee. Views and opinions expressed in this email are those
of the individual sender and are not necessarily the views and opinions
of CITEC unless the sender expressly states that such views and opinions
are those of CITEC. The privilege and confidentiality associated with
this email and attachments will not be waived, lost or rescinded by
reason of mistaken delivery. Should you receive this email by mistake,
please notify the sender by return email then delete the email from your
computer system. You must not use, copy, modify, print, or distribute
the email or the information and attachments contained within same to
any third party. CITEC does not accept any liability in respect of
viruses or computer problems experienced by the recipient through access
gained to this email and its attachments.


This email has been scanned for viruses by the CITEC Email Anti-Virus 
service powered by IronPort(r)
 


This email and associated attachments may contain confidential and privileged 
CITEC information that is provided solely for the use of the intended 
addressee. Views and opinions expressed in this email are those of the 
individual sender and are not necessarily the views and opinions of CITEC 
unless the sender expressly states that such views and opinions are those of 
CITEC. The privilege and confidentiality associated with this email and 
attachments will not be waived, lost or rescinded by reason of mistaken 
delivery. Should you receive this email by mistake, please notify the sen

Re: maven-changes-plugin 2.0-beta-2

[Savita_p_m]

Hi Adam,

Where u able to fix this problem, even I am facing the same problem. Can you
please let me know how did u resolve it,

I am getting the following error when I  try to connect to Jira application
running on SSL

 sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
vali
d certification path to requested target

I did configure the Jirauser ,jirapassword,webuser and webpassword. and if I
copy past the url to the browser it works.

Regards
Savita



Adam Hardy-4 wrote:
> 
> I'm sorry, I saw those when I first started looking, couldn't see how to 
> incorporate them in the pom.xml, went off looking for examples and all I 
> ended up with was the  node I mentioned. Forgot about 
> these ones.
> 
> I'll see if I can work out what the xml should look like.
> 
> 
> Regards
> Adam
> 
> Dennis Lundberg wrote:
>> Adam Hardy wrote:
>>> maven-changes-plugin can generate JIRA reports according to its 
>>> documentation but I'm having a hard time setting it up - the docs on 
>>> maven.apache.org specify an issueManagement config node and that's 
>>> about it.
>> 
>> See this page for info on all configuration options for the jira-report:
>> 
>> http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html
>> 
>> 
>>>  From the mvn output though it looks like there's alot more going on 
>>> than I know about, and I guess I need to find a way to specify project 
>>> ids, server usernames & passwords and so forth.
>>>
>>> The output I see on the console is below, but these are the main 
>>> problems I see:
>>>
>>> - there's a suspicious looking warning: [WARNING] Error loading report 
>>> org.apache.maven.jira.JiraMojo - AbstractMethodError:
>>> canGenerateReport()
>>>
>>> - my JIRA server runs on HTTPS and mvn has problems connecting - so 
>>> how can I specify my username and password?
>> 
>> See the link above.
>> 
>>> - mvn also can't find a log4j logger for HttpClient, which looks like 
>>> it is caching URLs from previous attempts! Where can I put
>>>
>>> The only settings I can work out for my pom for this are:
>>>
>>> 
>>>   JIRA
>>>   
>>> https://support.nomadsoft.com/jira/BrowseProject.jspa?id=10060
>>> 
>>>
>>>
>>>
>>> [INFO] [site:site]
>>> [WARNING] Error loading report 
>>> org.apache.maven.plugin.taglist.TagListReport - AbstractMethodError: 
>>> canGenerateReport()
>>> [WARNING] Error loading report org.apache.maven.changes.ChangesMojo - 
>>> AbstractMethodError: canGenerateReport()
>>> [WARNING] Error loading report org.apache.maven.jira.JiraMojo - 
>>> AbstractMethodError: canGenerateReport()
>>> [WARNING] No URL defined for the project - decoration links will not 
>>> be resolved
>>> [INFO] Skipped "Jira Report" report, file "jira-report.html" already 
>>> exists for the English version.
>>> [INFO] Generate "Tag List" report.
>>> [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 
>>> got 0
>>> [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
>>> [INFO] Generate "Continuous Integration" report.
>>> [INFO] Generate "Dependencies" report.
>>> [INFO] Generate "Issue Tracking" report.
>>> [INFO] Generate "Project License" report.
>>> [INFO] Generate "Mailing Lists" report.
>>> [INFO] Generate "Source Repository" report.
>>> [INFO] Generate "Project Team" report.
>>> [INFO] Generate "Changes Report Plugin" report.
>>> [ERROR] Cannot find the Changes XML file.
>>> [INFO] Generate "Jira Report Plugin" report.
>>> log4j:WARN No appenders could be found for logger 
>>> (org.apache.commons.httpclient.HttpClient).
>>> log4j:WARN Please initialize the log4j system properly.
>>> [INFO] Jira lives at: https://support.nomadsoft.com/jira
>>> [INFO] Downloading 
>>> https://support.nomadsoft.com/jira/secure/IssueNavigator.jspa?view=rss&pid=10060&sorter/field=created&sorter/order=DESC&sorter/field=prior
>>>  
>>>
>>> ity&sorter/order=DESC&tempMax=100&reset=true&decorator=none
>>> [ERROR] Error downloading issues from JIRA. Cause is 
>>> sun.security.validator.ValidatorException: PKIX path building failed: 
>>> sun.security.provider.certpath.Sun
>>> CertPathBuilderException: unable to find valid certification path to 
>>> requested target
>>> java.io.FileNotFoundException: c:\projects\soa\target\jira-results.xml 
>>> (The system cannot find the file specified)
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/M2-%3A-Maven-changes-plugin-%3A-jira-MCHANGES-42-fixed-2.0-beta2---tp9617170s177p15218138.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

site generation links modules in staging but uses wrong link when deploy

[Brice Lambi]

Hello,

I have a project with sub-projects.  When I run 'mvn site-deploy' it will
deploy the project but the "modules" links on the left link to
http://maven.apache.org.  When I do 'mvn site:stage' it works as expected
and the "modules" links properly link to the corresponding sub-directory.
Has anyone else had this problem?

Thanks,
Brice

Re: maven plugin for Checkstyle 4.4 availability

[Dennis Lundberg]

treese wrote:

I saw postings about getting snapshot plugin for checkstyle 4.3, so when will
one be available for checkstyle 4.4?


When there is a 4.4 version of Checkstyle in the central repo that we 
can use. Please ping the folks over at the Checkstyle project if you 
want this to happen. I have previously supplied them with the necessary 
tools to create an upload bundle.


--
Dennis Lundberg

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

Re: maven-eclipse-plugin 2.5 coming soon

[Arnaud HERITIER]

Yes I understand when you have only one project.
But you have only one level of modules or eclipse accept to have its
projects in several levels of subdirectories (for example root/a/b/pom.xml)
?

Arnaud

On Jan 31, 2008 11:06 PM, Dan Tran <[EMAIL PROTECTED]> wrote:

> Thanks, In fact my use case is a good one.  I have a team of 20
> developers on the same project, same eclispe workspace
> configuration ( ie same code style setup), and the workspace
> configuration is at the sameplace for all developers ( which is at the
> root pom level).
>
> This works out great.  ( no argument where to put the workspace ).
>
>
> Thank you for putting lots of works this plugin.
>
>
> -D
>
>
>
> On Jan 31, 2008 1:12 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > I didn't see this usage to have the eclipse workspace in the root
> directory
> > of your project. But why not ;-)
> > Effectively, in your case you call configure-workspace only in this
> > directory and not in sub-modules.
> > In all cases it's not normal that a bad workspace directory break the
> > eclipse:eclipse goal. It should work like it did before.
> > I thought also to add a switch parameter to say to the eclipse:eclipse
> goal
> > if it should read the workspace to find others projects or not.
> > I reopened  the issue : http://jira.codehaus.org/browse/MECLIPSE-344
> >
> > Arnaud
> >
> >
> > On Jan 31, 2008 9:57 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> >
> > > On Jan 31, 2008 12:30 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > > > There's something I don't understand.
> > > > The workspace parameter used in eclipse:configure-workspace and in
> > > > eclipse:add-maven-repo (which now deprecated by configure-workspace)
> has
> > > to
> > > > point to your workspace directory of eclipse. Not your project
> directory
> > > ?
> > >
> > > I mean ${workspace} should point to directory where you want
> > > eclipse:configure-workspace to create eclipse's workspace directory
> > > (ie .metadata) It workout nicely for my team to point ${workspace} to
> > > ${basedir} since configure-workspace goal only works
> > > at the top level.
> > >
> > >
> > > > Generally this parameter is defined in command line or with a
> property
> > > set
> > > > in the user's settings (or hardcoded if all your team has the same
> > > > directories layout).
> > > > And this is the same directory that we need in eclipse:eclipse, that
> why
> > > I
> > > > renamed it to have the same parameter name.
> > > >
> > > > Arnaud
> > > >
> > > >
> > > > On Jan 31, 2008 9:14 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > I have ${basedir} to point to the top
> directory
> > > > > of my multi module project.
> > > > > This element used to be recognizable ONLY  by
> > > > > add-maven-repo/configure-workspace mojos.
> > > > >
> > > > > however, in 2.5 eclipse goal now also recorgizes it at well.
>  Perhaps
> > > > > eclipse:eclipse goal should have a different mojo's field name for
> > > > > its own's workspace configuration? ( ie projectWorkspace )
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > > -D
> > > > >
> > > > >
> > > > > On Jan 31, 2008 10:32 AM, Arnaud HERITIER <[EMAIL PROTECTED]>
> wrote:
> > > > > > We have to document it. It's due to the workspace configuration
> > > > > parameter.
> > > > > > workspace is now recognized by the eclipse:eclipse goal to find
> > > others
> > > > > > projects :
> > > > > > http://jira.codehaus.org/browse/MECLIPSE-344
> > > > > > it should define where is your eclipse workspace.
> > > > > > Why did you use it with ${basedir}?
> > > > > > I'll see why the goal fails if the workspace parameter is wrong.
> It
> > > > > should
> > > > > > warn us and ignore it.
> > > > > >
> > > > > > Arnaud
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Jan 31, 2008 6:41 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > > I ran into problem during eclipse:eclipse
> > > > > > >
> > > > > > > here is my configuration
> > > > > > >
> > > > > > >
> > > > > > >  maven-eclipse-plugin
> > > > > > >  2.5-SNAPSHOT
> > > > > > >  
> > > > > > >${basedir}
> > > > > > >1.5
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/optional/eclipse-config/maven-styles.xml
> > > > > > >
> > > > > > >  
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> ===
> > > > > > > here is stack trace in one of my module
> > > > > > >
> > > > > > > [INFO] Building ipl-migrate
> > > > > > > [INFO]task-segment: [eclipse:eclipse]
> > > > > > > [INFO]
> > > > > > >
> > > > >
> > >
> 
> > > > > > > [INFO] Preparing eclipse:eclipse
> > > > > > > [INFO] No goals needed for project - skipping
> > > > > > 

Re: maven-eclipse-plugin 2.5 coming soon

[Dan Tran]

Thanks, In fact my use case is a good one.  I have a team of 20
developers on the same project, same eclispe workspace
configuration ( ie same code style setup), and the workspace
configuration is at the sameplace for all developers ( which is at the
root pom level).

This works out great.  ( no argument where to put the workspace ).


Thank you for putting lots of works this plugin.


-D



On Jan 31, 2008 1:12 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> I didn't see this usage to have the eclipse workspace in the root directory
> of your project. But why not ;-)
> Effectively, in your case you call configure-workspace only in this
> directory and not in sub-modules.
> In all cases it's not normal that a bad workspace directory break the
> eclipse:eclipse goal. It should work like it did before.
> I thought also to add a switch parameter to say to the eclipse:eclipse goal
> if it should read the workspace to find others projects or not.
> I reopened  the issue : http://jira.codehaus.org/browse/MECLIPSE-344
>
> Arnaud
>
>
> On Jan 31, 2008 9:57 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
>
> > On Jan 31, 2008 12:30 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > > There's something I don't understand.
> > > The workspace parameter used in eclipse:configure-workspace and in
> > > eclipse:add-maven-repo (which now deprecated by configure-workspace) has
> > to
> > > point to your workspace directory of eclipse. Not your project directory
> > ?
> >
> > I mean ${workspace} should point to directory where you want
> > eclipse:configure-workspace to create eclipse's workspace directory
> > (ie .metadata) It workout nicely for my team to point ${workspace} to
> > ${basedir} since configure-workspace goal only works
> > at the top level.
> >
> >
> > > Generally this parameter is defined in command line or with a property
> > set
> > > in the user's settings (or hardcoded if all your team has the same
> > > directories layout).
> > > And this is the same directory that we need in eclipse:eclipse, that why
> > I
> > > renamed it to have the same parameter name.
> > >
> > > Arnaud
> > >
> > >
> > > On Jan 31, 2008 9:14 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > >
> > > > I have ${basedir} to point to the top directory
> > > > of my multi module project.
> > > > This element used to be recognizable ONLY  by
> > > > add-maven-repo/configure-workspace mojos.
> > > >
> > > > however, in 2.5 eclipse goal now also recorgizes it at well.  Perhaps
> > > > eclipse:eclipse goal should have a different mojo's field name for
> > > > its own's workspace configuration? ( ie projectWorkspace )
> > > >
> > > > Thanks
> > > >
> > > >
> > > > -D
> > > >
> > > >
> > > > On Jan 31, 2008 10:32 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > > > > We have to document it. It's due to the workspace configuration
> > > > parameter.
> > > > > workspace is now recognized by the eclipse:eclipse goal to find
> > others
> > > > > projects :
> > > > > http://jira.codehaus.org/browse/MECLIPSE-344
> > > > > it should define where is your eclipse workspace.
> > > > > Why did you use it with ${basedir}?
> > > > > I'll see why the goal fails if the workspace parameter is wrong. It
> > > > should
> > > > > warn us and ignore it.
> > > > >
> > > > > Arnaud
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Jan 31, 2008 6:41 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > > I ran into problem during eclipse:eclipse
> > > > > >
> > > > > > here is my configuration
> > > > > >
> > > > > >
> > > > > >  maven-eclipse-plugin
> > > > > >  2.5-SNAPSHOT
> > > > > >  
> > > > > >${basedir}
> > > > > >1.5
> > > > > >
> > > > > >
> > > > > >
> > > >
> > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/optional/eclipse-config/maven-styles.xml
> > > > > >
> > > > > >  
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > ===
> > > > > > here is stack trace in one of my module
> > > > > >
> > > > > > [INFO] Building ipl-migrate
> > > > > > [INFO]task-segment: [eclipse:eclipse]
> > > > > > [INFO]
> > > > > >
> > > >
> > 
> > > > > > [INFO] Preparing eclipse:eclipse
> > > > > > [INFO] No goals needed for project - skipping
> > > > > > [INFO] [eclipse:eclipse]
> > > > > > [INFO] Adding support for WTP version 1.5.
> > > > > > [ERROR] Could not read workspace JRE preferences
> > > > > > java.io.FileNotFoundException:
> > > > > > C:\dev\iplocks\va\ipl-migrate\.metadata\.plugins\
> > > > > > org.eclipse.core.runtime\.settings\org.eclipse.jdt.launching.prefs
> > (The
> > > > > > system c
> > > > > > annot find the path specified)
> > > > > >at java.io.FileInputStream.open(Native Method)
> > > > > >at java.io.FileInputStream.(FileInputStream.java:106)
> > > >

Re: maven-eclipse-plugin 2.5 coming soon

[Siarhei Dudzin]

Arnaud, please don't loose this one
http://jira.codehaus.org/browse/MECLIPSE-316 :)
There is also a minor RAD issue coming, I'll put it in JIRA in a few...

Siarhei

unsolicited multiple executions of my plugin

[Nourredine Rouibah]

Hi,

I have a home made plugin that I wanted to execute at
phase:generate-sources.

When I build my project I get 3 executions of my plugin:

1- one for the generate-sources phase and that produces my project jar.
2- one when I generate the javadoc in a jar.
3- one when I package my sources in a jar.

For each call the plugin is called with the same arguments so it's like (1)
is executed 3 times correctly.

I expected the plugin to be called only once at the generate:sources phase.

-- 
nr.

Re: maven-eclipse-plugin 2.5 coming soon

[Arnaud HERITIER]

I didn't see this usage to have the eclipse workspace in the root directory
of your project. But why not ;-)
Effectively, in your case you call configure-workspace only in this
directory and not in sub-modules.
In all cases it's not normal that a bad workspace directory break the
eclipse:eclipse goal. It should work like it did before.
I thought also to add a switch parameter to say to the eclipse:eclipse goal
if it should read the workspace to find others projects or not.
I reopened  the issue : http://jira.codehaus.org/browse/MECLIPSE-344

Arnaud

On Jan 31, 2008 9:57 PM, Dan Tran <[EMAIL PROTECTED]> wrote:

> On Jan 31, 2008 12:30 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > There's something I don't understand.
> > The workspace parameter used in eclipse:configure-workspace and in
> > eclipse:add-maven-repo (which now deprecated by configure-workspace) has
> to
> > point to your workspace directory of eclipse. Not your project directory
> ?
>
> I mean ${workspace} should point to directory where you want
> eclipse:configure-workspace to create eclipse's workspace directory
> (ie .metadata) It workout nicely for my team to point ${workspace} to
> ${basedir} since configure-workspace goal only works
> at the top level.
>
>
> > Generally this parameter is defined in command line or with a property
> set
> > in the user's settings (or hardcoded if all your team has the same
> > directories layout).
> > And this is the same directory that we need in eclipse:eclipse, that why
> I
> > renamed it to have the same parameter name.
> >
> > Arnaud
> >
> >
> > On Jan 31, 2008 9:14 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> >
> > > I have ${basedir} to point to the top directory
> > > of my multi module project.
> > > This element used to be recognizable ONLY  by
> > > add-maven-repo/configure-workspace mojos.
> > >
> > > however, in 2.5 eclipse goal now also recorgizes it at well.  Perhaps
> > > eclipse:eclipse goal should have a different mojo's field name for
> > > its own's workspace configuration? ( ie projectWorkspace )
> > >
> > > Thanks
> > >
> > >
> > > -D
> > >
> > >
> > > On Jan 31, 2008 10:32 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > > > We have to document it. It's due to the workspace configuration
> > > parameter.
> > > > workspace is now recognized by the eclipse:eclipse goal to find
> others
> > > > projects :
> > > > http://jira.codehaus.org/browse/MECLIPSE-344
> > > > it should define where is your eclipse workspace.
> > > > Why did you use it with ${basedir}?
> > > > I'll see why the goal fails if the workspace parameter is wrong. It
> > > should
> > > > warn us and ignore it.
> > > >
> > > > Arnaud
> > > >
> > > >
> > > >
> > > >
> > > > On Jan 31, 2008 6:41 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > I ran into problem during eclipse:eclipse
> > > > >
> > > > > here is my configuration
> > > > >
> > > > >
> > > > >  maven-eclipse-plugin
> > > > >  2.5-SNAPSHOT
> > > > >  
> > > > >${basedir}
> > > > >1.5
> > > > >
> > > > >
> > > > >
> > >
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/optional/eclipse-config/maven-styles.xml
> > > > >
> > > > >  
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> ===
> > > > > here is stack trace in one of my module
> > > > >
> > > > > [INFO] Building ipl-migrate
> > > > > [INFO]task-segment: [eclipse:eclipse]
> > > > > [INFO]
> > > > >
> > >
> 
> > > > > [INFO] Preparing eclipse:eclipse
> > > > > [INFO] No goals needed for project - skipping
> > > > > [INFO] [eclipse:eclipse]
> > > > > [INFO] Adding support for WTP version 1.5.
> > > > > [ERROR] Could not read workspace JRE preferences
> > > > > java.io.FileNotFoundException:
> > > > > C:\dev\iplocks\va\ipl-migrate\.metadata\.plugins\
> > > > > org.eclipse.core.runtime\.settings\org.eclipse.jdt.launching.prefs
> (The
> > > > > system c
> > > > > annot find the path specified)
> > > > >at java.io.FileInputStream.open(Native Method)
> > > > >at java.io.FileInputStream.(FileInputStream.java:106)
> > > > >at
> > > > >
> org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readAva
> > > > > ilableJREs(ReadWorkspaceLocations.java:424)
> > > > >at
> > > > >
> org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.detectD
> > > > > efaultJREContaigner(ReadWorkspaceLocations.java:191)
> > > > >at
> > > > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.init
> (Re
> > > > > adWorkspaceLocations.java:89)
> > > > >at
> > > > >
> org.apache.maven.plugin.eclipse.EclipsePlugin.getWorkspaceConfigurati
> > > > > on(EclipsePlugin.java:1343)
> > > > >at
> > > > >
> org.apache.maven.plugin.eclipse.EclipsePlugin.fillDefaultClasspathCon
> > > >

Re: maven-eclipse-plugin 2.5 coming soon

[Dan Tran]

On Jan 31, 2008 12:30 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> There's something I don't understand.
> The workspace parameter used in eclipse:configure-workspace and in
> eclipse:add-maven-repo (which now deprecated by configure-workspace) has to
> point to your workspace directory of eclipse. Not your project directory ?

I mean ${workspace} should point to directory where you want
eclipse:configure-workspace to create eclipse's workspace directory
(ie .metadata) It workout nicely for my team to point ${workspace} to
${basedir} since configure-workspace goal only works
at the top level.


> Generally this parameter is defined in command line or with a property set
> in the user's settings (or hardcoded if all your team has the same
> directories layout).
> And this is the same directory that we need in eclipse:eclipse, that why I
> renamed it to have the same parameter name.
>
> Arnaud
>
>
> On Jan 31, 2008 9:14 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
>
> > I have ${basedir} to point to the top directory
> > of my multi module project.
> > This element used to be recognizable ONLY  by
> > add-maven-repo/configure-workspace mojos.
> >
> > however, in 2.5 eclipse goal now also recorgizes it at well.  Perhaps
> > eclipse:eclipse goal should have a different mojo's field name for
> > its own's workspace configuration? ( ie projectWorkspace )
> >
> > Thanks
> >
> >
> > -D
> >
> >
> > On Jan 31, 2008 10:32 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > > We have to document it. It's due to the workspace configuration
> > parameter.
> > > workspace is now recognized by the eclipse:eclipse goal to find others
> > > projects :
> > > http://jira.codehaus.org/browse/MECLIPSE-344
> > > it should define where is your eclipse workspace.
> > > Why did you use it with ${basedir}?
> > > I'll see why the goal fails if the workspace parameter is wrong. It
> > should
> > > warn us and ignore it.
> > >
> > > Arnaud
> > >
> > >
> > >
> > >
> > > On Jan 31, 2008 6:41 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> > >
> > > > I ran into problem during eclipse:eclipse
> > > >
> > > > here is my configuration
> > > >
> > > >
> > > >  maven-eclipse-plugin
> > > >  2.5-SNAPSHOT
> > > >  
> > > >${basedir}
> > > >1.5
> > > >
> > > >
> > > >
> > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/optional/eclipse-config/maven-styles.xml
> > > >
> > > >  
> > > >
> > > >
> > > >
> > > >
> > > >
> > ===
> > > > here is stack trace in one of my module
> > > >
> > > > [INFO] Building ipl-migrate
> > > > [INFO]task-segment: [eclipse:eclipse]
> > > > [INFO]
> > > >
> > 
> > > > [INFO] Preparing eclipse:eclipse
> > > > [INFO] No goals needed for project - skipping
> > > > [INFO] [eclipse:eclipse]
> > > > [INFO] Adding support for WTP version 1.5.
> > > > [ERROR] Could not read workspace JRE preferences
> > > > java.io.FileNotFoundException:
> > > > C:\dev\iplocks\va\ipl-migrate\.metadata\.plugins\
> > > > org.eclipse.core.runtime\.settings\org.eclipse.jdt.launching.prefs(The
> > > > system c
> > > > annot find the path specified)
> > > >at java.io.FileInputStream.open(Native Method)
> > > >at java.io.FileInputStream.(FileInputStream.java:106)
> > > >at
> > > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readAva
> > > > ilableJREs(ReadWorkspaceLocations.java:424)
> > > >at
> > > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.detectD
> > > > efaultJREContaigner(ReadWorkspaceLocations.java:191)
> > > >at
> > > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.init(Re
> > > > adWorkspaceLocations.java:89)
> > > >at
> > > > org.apache.maven.plugin.eclipse.EclipsePlugin.getWorkspaceConfigurati
> > > > on(EclipsePlugin.java:1343)
> > > >at
> > > > org.apache.maven.plugin.eclipse.EclipsePlugin.fillDefaultClasspathCon
> > > > tainers(EclipsePlugin.java:1092)
> > > >at org.apache.maven.plugin.eclipse.EclipsePlugin.setup(
> > > > EclipsePlugin.jav
> > > > a:662)
> > > >at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute
> > > > (AbstractId
> > > > eSupportMojo.java:502)
> > > >at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> > > > (DefaultPlugi
> > > > nManager.java:447)
> > > >at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> > > > (Defa
> > > > ultLifecycleExecutor.java:539)
> > > >at
> > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> > > > Goal(DefaultLifecycleExecutor.java:493)
> > > >at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> > > > (Defau
> > > > ltLifecycleExecutor.java:463)
> > > >at
> > > > org.apache.maven.lifecyc

Re: maven-eclipse-plugin 2.5 coming soon

[Arnaud HERITIER]

We effectively resolved all issues with a greater priority ;-)
I will have a look at it to see if it's easy to add with a test case (and if
it doesn't break something).

Arnaud

On Jan 31, 2008 9:00 PM, Jim Sellers <[EMAIL PROTECTED]> wrote:

> Do you know if there are plans to include MECLIPSE-79 in 2.5?  I believe
> that it's the most voted for issue and it has a patch attached.
> http://jira.codehaus.org/browse/MECLIPSE-79
>
> Or does anyone know why it's applied?
>
> Thanks for your time,
> Jim
>
>
> On 1/31/08, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> >
> > Hi all,
> >
> >   We fixed a lot of issues for the version 2.5 of the eclipse plugin and
> > we'll launch the vote to release it in few days.
> >   In this version we improved a lot the support for RAD 6 / RAD 7 and we
> > added  new features like WTP 2.0 support,  MyEclipse
> > support,  dependencies
> > to projects in your projects, ... and more.
> >   You can find the complete change log here :
> >
> >
> http://jira.codehaus.org/browse/MECLIPSE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
> >   If you want to test it before the launch of the vote you have to
> define
> > and activate this profile :
> >
> > 
> >   apache.snapshots
> >   
> > 
> >   
> > false
> >   
> >   
> >   apache.snapshots
> >   Maven Snapshots
> >   http://people.apache.org/maven-snapshot-repository
> > 
> >   
> >   
> > 
> >   
> > false
> >   
> >   
> >   apache.plugin.snapshots
> >   Maven Plugin Snapshots
> >   http://people.apache.org/maven-snapshot-repository
> > 
> >   
> > 
> >
> > And then you can call this command :
> >
> >   mvn org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
> >
> > (or another mojo).
> >
> > The documentation of the 2.5 was previously deployed by error, thus I
> just
> > updated it to give you the new version.
> >
> > Cheers,
> >
> > Arnaud
> >
> > --
> > ..
> > Arnaud HERITIER
> > ..
> > OCTO Technology - aheritier AT octo DOT com
> > www.octo.com | blog.octo.com
> > ..
> > ASF - aheritier AT apache DOT org
> > www.apache.org | maven.apache.org
> > ...
> >
>



-- 
..
Arnaud HERITIER
..
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...

Re: maven-eclipse-plugin 2.5 coming soon

[Arnaud HERITIER]

There's something I don't understand.
The workspace parameter used in eclipse:configure-workspace and in
eclipse:add-maven-repo (which now deprecated by configure-workspace) has to
point to your workspace directory of eclipse. Not your project directory ?
Generally this parameter is defined in command line or with a property set
in the user's settings (or hardcoded if all your team has the same
directories layout).
And this is the same directory that we need in eclipse:eclipse, that why I
renamed it to have the same parameter name.

Arnaud

On Jan 31, 2008 9:14 PM, Dan Tran <[EMAIL PROTECTED]> wrote:

> I have ${basedir} to point to the top directory
> of my multi module project.
> This element used to be recognizable ONLY  by
> add-maven-repo/configure-workspace mojos.
>
> however, in 2.5 eclipse goal now also recorgizes it at well.  Perhaps
> eclipse:eclipse goal should have a different mojo's field name for
> its own's workspace configuration? ( ie projectWorkspace )
>
> Thanks
>
>
> -D
>
>
> On Jan 31, 2008 10:32 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > We have to document it. It's due to the workspace configuration
> parameter.
> > workspace is now recognized by the eclipse:eclipse goal to find others
> > projects :
> > http://jira.codehaus.org/browse/MECLIPSE-344
> > it should define where is your eclipse workspace.
> > Why did you use it with ${basedir}?
> > I'll see why the goal fails if the workspace parameter is wrong. It
> should
> > warn us and ignore it.
> >
> > Arnaud
> >
> >
> >
> >
> > On Jan 31, 2008 6:41 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
> >
> > > I ran into problem during eclipse:eclipse
> > >
> > > here is my configuration
> > >
> > >
> > >  maven-eclipse-plugin
> > >  2.5-SNAPSHOT
> > >  
> > >${basedir}
> > >1.5
> > >
> > >
> > >
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/optional/eclipse-config/maven-styles.xml
> > >
> > >  
> > >
> > >
> > >
> > >
> > >
> ===
> > > here is stack trace in one of my module
> > >
> > > [INFO] Building ipl-migrate
> > > [INFO]task-segment: [eclipse:eclipse]
> > > [INFO]
> > >
> 
> > > [INFO] Preparing eclipse:eclipse
> > > [INFO] No goals needed for project - skipping
> > > [INFO] [eclipse:eclipse]
> > > [INFO] Adding support for WTP version 1.5.
> > > [ERROR] Could not read workspace JRE preferences
> > > java.io.FileNotFoundException:
> > > C:\dev\iplocks\va\ipl-migrate\.metadata\.plugins\
> > > org.eclipse.core.runtime\.settings\org.eclipse.jdt.launching.prefs(The
> > > system c
> > > annot find the path specified)
> > >at java.io.FileInputStream.open(Native Method)
> > >at java.io.FileInputStream.(FileInputStream.java:106)
> > >at
> > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readAva
> > > ilableJREs(ReadWorkspaceLocations.java:424)
> > >at
> > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.detectD
> > > efaultJREContaigner(ReadWorkspaceLocations.java:191)
> > >at
> > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.init(Re
> > > adWorkspaceLocations.java:89)
> > >at
> > > org.apache.maven.plugin.eclipse.EclipsePlugin.getWorkspaceConfigurati
> > > on(EclipsePlugin.java:1343)
> > >at
> > > org.apache.maven.plugin.eclipse.EclipsePlugin.fillDefaultClasspathCon
> > > tainers(EclipsePlugin.java:1092)
> > >at org.apache.maven.plugin.eclipse.EclipsePlugin.setup(
> > > EclipsePlugin.jav
> > > a:662)
> > >at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute
> > > (AbstractId
> > > eSupportMojo.java:502)
> > >at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> > > (DefaultPlugi
> > > nManager.java:447)
> > >at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> > > (Defa
> > > ultLifecycleExecutor.java:539)
> > >at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> > > Goal(DefaultLifecycleExecutor.java:493)
> > >at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> > > (Defau
> > > ltLifecycleExecutor.java:463)
> > >at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> > > dleFailures(DefaultLifecycleExecutor.java:311)
> > >at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> > > ts(DefaultLifecycleExecutor.java:278)
> > >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> > > (DefaultLi
> > > fecycleExecutor.java:143)
> > >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java
> :333)
> > >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> > >at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> > 

Re: [maven-checkstyle-plugin] Including test classes in report?

[Wayne Fay]

>From the docs:
includeTestSourceDirectory Include or not the test source directory to
be used for Checkstyle
Type: boolean
Since: 2.2

And you're using version 2.1.

Wayne

On 1/31/08, Hoover, William <[EMAIL PROTECTED]> wrote:
> Thanks for the hint!
>
> I tried the following, but it still does not work. Any ideas why?
>
>
>
>
>org.apache.maven.plugins
>
> maven-checkstyle-plugin
>2.1
>
>
> nemours-checkstyle.xml
>
> true
>
>
>
>
>
> -Original Message-
> From: Nick Stolwijk [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 31, 2008 2:54 PM
> To: Maven Users List
> Subject: Re: [maven-checkstyle-plugin] Including test classes in report?
>
>
> I see you can only give one sourcedirectory, but you can add the
> parameter "includeTestSourceDirectory" [1].
>
> Hth,
>
> Nick Stolwijk
>
> [1]
> http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#includeTestSourceDirectory
>
> Hoover, William wrote:
> > Does anyone know a way to include test classes (src/test/java) in the 
> > checkstyle report? I am only recieving results for packaged classes 
> > (src/main/java)
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: maven-eclipse-plugin 2.5 coming soon

[Dan Tran]

I have ${basedir} to point to the top directory
of my multi module project.
This element used to be recognizable ONLY  by
add-maven-repo/configure-workspace mojos.

however, in 2.5 eclipse goal now also recorgizes it at well.  Perhaps
eclipse:eclipse goal should have a different mojo's field name for
its own's workspace configuration? ( ie projectWorkspace )

Thanks


-D


On Jan 31, 2008 10:32 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> We have to document it. It's due to the workspace configuration parameter.
> workspace is now recognized by the eclipse:eclipse goal to find others
> projects :
> http://jira.codehaus.org/browse/MECLIPSE-344
> it should define where is your eclipse workspace.
> Why did you use it with ${basedir}?
> I'll see why the goal fails if the workspace parameter is wrong. It should
> warn us and ignore it.
>
> Arnaud
>
>
>
>
> On Jan 31, 2008 6:41 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
>
> > I ran into problem during eclipse:eclipse
> >
> > here is my configuration
> >
> >
> >  maven-eclipse-plugin
> >  2.5-SNAPSHOT
> >  
> >${basedir}
> >1.5
> >
> >
> > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/optional/eclipse-config/maven-styles.xml
> >
> >  
> >
> >
> >
> >
> > ===
> > here is stack trace in one of my module
> >
> > [INFO] Building ipl-migrate
> > [INFO]task-segment: [eclipse:eclipse]
> > [INFO]
> > 
> > [INFO] Preparing eclipse:eclipse
> > [INFO] No goals needed for project - skipping
> > [INFO] [eclipse:eclipse]
> > [INFO] Adding support for WTP version 1.5.
> > [ERROR] Could not read workspace JRE preferences
> > java.io.FileNotFoundException:
> > C:\dev\iplocks\va\ipl-migrate\.metadata\.plugins\
> > org.eclipse.core.runtime\.settings\org.eclipse.jdt.launching.prefs (The
> > system c
> > annot find the path specified)
> >at java.io.FileInputStream.open(Native Method)
> >at java.io.FileInputStream.(FileInputStream.java:106)
> >at
> > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readAva
> > ilableJREs(ReadWorkspaceLocations.java:424)
> >at
> > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.detectD
> > efaultJREContaigner(ReadWorkspaceLocations.java:191)
> >at
> > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.init(Re
> > adWorkspaceLocations.java:89)
> >at
> > org.apache.maven.plugin.eclipse.EclipsePlugin.getWorkspaceConfigurati
> > on(EclipsePlugin.java:1343)
> >at
> > org.apache.maven.plugin.eclipse.EclipsePlugin.fillDefaultClasspathCon
> > tainers(EclipsePlugin.java:1092)
> >at org.apache.maven.plugin.eclipse.EclipsePlugin.setup(
> > EclipsePlugin.jav
> > a:662)
> >at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute
> > (AbstractId
> > eSupportMojo.java:502)
> >at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> > (DefaultPlugi
> > nManager.java:447)
> >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> > (Defa
> > ultLifecycleExecutor.java:539)
> >at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> > Goal(DefaultLifecycleExecutor.java:493)
> >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> > (Defau
> > ltLifecycleExecutor.java:463)
> >at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> > dleFailures(DefaultLifecycleExecutor.java:311)
> >at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> > ts(DefaultLifecycleExecutor.java:278)
> >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> > (DefaultLi
> > fecycleExecutor.java:143)
> >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> >at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at sun.reflect.NativeMethodAccessorImpl.invoke
> > (NativeMethodAccessorImpl.
> > java:39)
> >at sun.reflect.DelegatingMethodAccessorImpl.invoke
> > (DelegatingMethodAcces
> > sorImpl.java:25)
> >at java.lang.reflect.Method.invoke(Method.java:585)
> >at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
> > :315)
> >at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
> > :430)
> >
> >at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> > [ERROR] Could not read workspace wtp server runtimes preferences :
> > C:\dev\iplock
> >
> > s\va\ipl-migrate\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclip

Re: maven renaming jar files

[Stephen Connolly]

Or if you are checking them in manually, at least use a different version
which includes your company name, e.g.

commons-logging
commins-logging
1.0-mycompany-1

That way maven will at least detect that these are different versions of the
same artifact and the version ranges and preferences should* let you pick
your one!

-Stephen

* Yes I know some people have issues with version ranges, etc. but there are
ways of making them work, or at least using a dependencyManagement section

On Jan 31, 2008 4:07 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:

> We've had more than one person show up on this list complaining about
> strange difficulties with Maven. After a bit of prodding, they tell us
> that they manually created their repo and the pom files, if they exist
> at all, are just GAV with no transitive deps. And then they're usually
> complaining about how Maven isn't working like they expected.
>
> I just want to make sure this happens to as few people as possible. If
> you know what you're doing and want to check-in some files, please do
> it, especially for things like Websphere and Weblogic that will never
> appear in the Central repo.
>
> But doing this for things like commons-* is a bad practice. Even if
> you know what you're doing, you probably should not be checking in
> files like these manually.
>
> Wayne
>
> On 1/31/08, Simon Kitching <[EMAIL PROTECTED]> wrote:
> > I've certainly done something similar in the past. To reduce network
> traffic, and to better control what libs are used, it is nice to have a
> repository on a local server hosting the jars you need.
> >
> > It is very tempting to just take the set of jars you have always been
> using (in an existing ant-based build process or similar) and just upload
> them to that new repository. It is certainly easier than finding a maven
> repository proxy application, and setting that up.
> >
> > I don't see a lot wrong with doing that - except that you do need to get
> the group ids right!
> >
> > Of course long-term, having a proper repository manager installed
> locally appears to be the right solution. Some day I have to get that
> organised for my workplace...
> >
> > Interesting to see that the war plugin does detect filename clashes; as
> discussed in another thread recently it appears that the dependency plugin
> does not...
> >
> > Regards,
> > Simon
> >
> >  Wayne Fay <[EMAIL PROTECTED]> schrieb:
> > > If you're using "mvn install" or "mvn deploy" to install/deploy common
> > > artifacts like commons-logging etc, then you're probably using Maven
> > > wrong.
> > >
> > > What you've described is exactly what the problem was. You had added
> > > c-l as a particular G/A/V and then c-l was coming in as a transitive
> > > dep under a different G/A/V. Since the plugin detected a name
> > > collision, it expanded the name to include the group as well, to make
> > > it unique.
> > >
> > > Why did you install/deploy commons-logging instead of simply adding a
> > > ? You're not the first person to report doing this, so I
> > > want to understand if there is a failure in the documentation
> > > somewhere or if new users are simply making poor assumptions about
> > > what Maven does.
> > >
> > > Wayne
> > >
> > > On 1/31/08, amit kumar <[EMAIL PROTECTED]> wrote:
> > > > I have overcome the problem. And guess know the reason for that,
> > > > actually at the time of creating the LAN maven repository, I have
> > > > installed common components under org.apache.commons groupId (
> > > > assuming the convention of groupId as package name ). So now when I
> > > > was including commons-logging as dependency in my pom.xml,
> > > > what I added to pom looked like
> > > >
> > > > org.apache.commons
> > > > commons-logging
> > > > 1.1
> > > >
> > > > But there was another dependency in my pom.xml which as
> > > > commons-logging as transitive dependency with same version, so what
> > > > was happening(probably) was that maven instead of overriding the jar
> > > > file was renaming it, may be because the jars were differently
> > > > identified as groupId+artifactId+version.
> > > > Still a little confused about my own explanation of the happenings
> :)
> > > >
> > > > Amit
> > > >
> > > > On Jan 30, 2008 9:51 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> > > > > Looks weird.
> > > > > Do you use a released version ? or the current snapshot ?
> > > > >
> > > > > Could you load an issue in jira with a simple project which
> reproduce this ?
> > > > >
> > > > > --
> > > > > Olivier
> > > > >
> > > > > 2008/1/30, amit kumar <[EMAIL PROTECTED]>:
> > > > >
> > > > > > Hi,.
> > > > > > When I am packaging a WAR project, I am seeing the following
> thing happening...
> > > > > >
> > > > > > [DEBUG] Processing: commons-logging-1.1.jar
> > > > > > [DEBUG] Duplicate found: commons-logging-1.1.jar
> > > > > > [DEBUG] Renamed to: commons-logging-commons-logging-1.1.jar
> > > > > >
> > > > > > Any idea why this happens and how to avoid this?
> > > > > > I am mentioning

Re: maven-eclipse-plugin 2.5 coming soon

[Jim Sellers]

Do you know if there are plans to include MECLIPSE-79 in 2.5?  I believe
that it's the most voted for issue and it has a patch attached.
http://jira.codehaus.org/browse/MECLIPSE-79

Or does anyone know why it's applied?

Thanks for your time,
Jim


On 1/31/08, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
>   We fixed a lot of issues for the version 2.5 of the eclipse plugin and
> we'll launch the vote to release it in few days.
>   In this version we improved a lot the support for RAD 6 / RAD 7 and we
> added  new features like WTP 2.0 support,  MyEclipse
> support,  dependencies
> to projects in your projects, ... and more.
>   You can find the complete change log here :
>
> http://jira.codehaus.org/browse/MECLIPSE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
>   If you want to test it before the launch of the vote you have to define
> and activate this profile :
>
> 
>   apache.snapshots
>   
> 
>   
> false
>   
>   
>   apache.snapshots
>   Maven Snapshots
>   http://people.apache.org/maven-snapshot-repository
> 
>   
>   
> 
>   
> false
>   
>   
>   apache.plugin.snapshots
>   Maven Plugin Snapshots
>   http://people.apache.org/maven-snapshot-repository
> 
>   
> 
>
> And then you can call this command :
>
>   mvn org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
>
> (or another mojo).
>
> The documentation of the 2.5 was previously deployed by error, thus I just
> updated it to give you the new version.
>
> Cheers,
>
> Arnaud
>
> --
> ..
> Arnaud HERITIER
> ..
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...
>

RE: [maven-checkstyle-plugin] Including test classes in report?

[Hoover, William]

Thanks for the hint!

I tried the following, but it still does not work. Any ideas why?




org.apache.maven.plugins
maven-checkstyle-plugin
2.1


nemours-checkstyle.xml

true





-Original Message-
From: Nick Stolwijk [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 31, 2008 2:54 PM
To: Maven Users List
Subject: Re: [maven-checkstyle-plugin] Including test classes in report?


I see you can only give one sourcedirectory, but you can add the 
parameter "includeTestSourceDirectory" [1].

Hth,

Nick Stolwijk

[1] 
http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#includeTestSourceDirectory

Hoover, William wrote:
> Does anyone know a way to include test classes (src/test/java) in the 
> checkstyle report? I am only recieving results for packaged classes 
> (src/main/java)
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>   

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



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

Re: [maven-checkstyle-plugin] Including test classes in report?

[Nick Stolwijk]

I see you can only give one sourcedirectory, but you can add the 
parameter "includeTestSourceDirectory" [1].


Hth,

Nick Stolwijk

[1] 
http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#includeTestSourceDirectory


Hoover, William wrote:

Does anyone know a way to include test classes (src/test/java) in the 
checkstyle report? I am only recieving results for packaged classes 
(src/main/java)


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


  


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

[maven-checkstyle-plugin] Including test classes in report?

[Hoover, William]

Does anyone know a way to include test classes (src/test/java) in the 
checkstyle report? I am only recieving results for packaged classes 
(src/main/java)


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

Re: Releasing a Project with Modules

[lsacco]

I'm having the same issue.  Can anyone help provide a solution?

Note that in my case the projects are all adjacent to each other in the
directory such that the Maven project has it's own directory rather than in
the root (due to Eclipse).  My modules are identified as following in the
POM:


../XXXCommon
../XXXService
../XXXWeb


Thanks,
Lou


wibbo wrote:
> 
> Hello,
> 
> I'm trying to use the release plugin to release a project with several
> modules. I managed to get it working that the versions of the parent
> project
> and the modules is being updated. I'm dealing with the issue that only the
> parent project is being uploaded to my SCM. Is it possible to upload the
> modules as well during the release of the parent project?
> 
> Thanks for any help!
> 
> Kind Regards,
> Thomas Tardy
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Releasing-a-Project-with-Modules-tp14720347s177p15211767.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Problems installing maven

[Lee Meador]

What version of Java is installed? For example, go to where you would type
"mvn -version" and type "java -version"

-- Lee

On Jan 31, 2008 8:49 AM, Alexander Petri <[EMAIL PROTECTED]> wrote:

> Hi,
>
>
>
> if i run "mvn" from console (i.e. mvn -version)  it gets the same output
> like
>
> if I call "java". Does anyone know what i did wrong?
>
>
>
> The Environmentpaths/Variables should be correct. Im using maven 2.0.8 and
> WinVista
>
>
>
> thx
>
>


-- 
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com

Re: maven-eclipse-plugin 2.5 coming soon

[Arnaud HERITIER]

We have to document it. It's due to the workspace configuration parameter.
workspace is now recognized by the eclipse:eclipse goal to find others
projects :
http://jira.codehaus.org/browse/MECLIPSE-344
it should define where is your eclipse workspace.
Why did you use it with ${basedir}?
I'll see why the goal fails if the workspace parameter is wrong. It should
warn us and ignore it.

Arnaud



On Jan 31, 2008 6:41 PM, Dan Tran <[EMAIL PROTECTED]> wrote:

> I ran into problem during eclipse:eclipse
>
> here is my configuration
>
>
>  maven-eclipse-plugin
>  2.5-SNAPSHOT
>  
>${basedir}
>1.5
>
>
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/optional/eclipse-config/maven-styles.xml
>
>  
>
>
>
>
> ===
> here is stack trace in one of my module
>
> [INFO] Building ipl-migrate
> [INFO]task-segment: [eclipse:eclipse]
> [INFO]
> 
> [INFO] Preparing eclipse:eclipse
> [INFO] No goals needed for project - skipping
> [INFO] [eclipse:eclipse]
> [INFO] Adding support for WTP version 1.5.
> [ERROR] Could not read workspace JRE preferences
> java.io.FileNotFoundException:
> C:\dev\iplocks\va\ipl-migrate\.metadata\.plugins\
> org.eclipse.core.runtime\.settings\org.eclipse.jdt.launching.prefs (The
> system c
> annot find the path specified)
>at java.io.FileInputStream.open(Native Method)
>at java.io.FileInputStream.(FileInputStream.java:106)
>at
> org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readAva
> ilableJREs(ReadWorkspaceLocations.java:424)
>at
> org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.detectD
> efaultJREContaigner(ReadWorkspaceLocations.java:191)
>at
> org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.init(Re
> adWorkspaceLocations.java:89)
>at
> org.apache.maven.plugin.eclipse.EclipsePlugin.getWorkspaceConfigurati
> on(EclipsePlugin.java:1343)
>at
> org.apache.maven.plugin.eclipse.EclipsePlugin.fillDefaultClasspathCon
> tainers(EclipsePlugin.java:1092)
>at org.apache.maven.plugin.eclipse.EclipsePlugin.setup(
> EclipsePlugin.jav
> a:662)
>at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute
> (AbstractId
> eSupportMojo.java:502)
>at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> (DefaultPlugi
> nManager.java:447)
>at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Defa
> ultLifecycleExecutor.java:539)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> Goal(DefaultLifecycleExecutor.java:493)
>at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (Defau
> ltLifecycleExecutor.java:463)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:311)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:278)
>at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (DefaultLi
> fecycleExecutor.java:143)
>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.
> java:39)
>at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAcces
> sorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:585)
>at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
> :315)
>at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
> :430)
>
>at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [ERROR] Could not read workspace wtp server runtimes preferences :
> C:\dev\iplock
>
> s\va\ipl-migrate\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclip
> se.wst.server.core.prefs (The system cannot find the path specified)
> [INFO] Using as WTP server : null
> [INFO] Adding default classpath contaigner:
> org.eclipse.jdt.launching.JRE_CONTAI
> NER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
> [INFO] Using source status cache: C:\dev\iplocks\va\target\mvn-
> eclipse-cache.pro
> perties
> [INFO] Wrote settings to
> C:\dev\iplocks\va\ipl-migrate\.settings\org.eclipse.jdt
> .core.prefs
> [INFO] Wrote Eclipse project for "ipl-migrate" to
> C:\dev\iplocks\va\ipl-migrate.
>
> On Jan 31, 2008 7:27 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> >  We fixed a lot of issues for the versi

Re: maven-eclipse-plugin 2.5 coming soon

[Dan Tran]

I ran into problem during eclipse:eclipse

here is my configuration


  maven-eclipse-plugin
  2.5-SNAPSHOT
  
${basedir}
1.5

  
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/optional/eclipse-config/maven-styles.xml

  




===
here is stack trace in one of my module

[INFO] Building ipl-migrate
[INFO]task-segment: [eclipse:eclipse]
[INFO] 
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse]
[INFO] Adding support for WTP version 1.5.
[ERROR] Could not read workspace JRE preferences
java.io.FileNotFoundException: C:\dev\iplocks\va\ipl-migrate\.metadata\.plugins\
org.eclipse.core.runtime\.settings\org.eclipse.jdt.launching.prefs (The system c
annot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:106)
at org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readAva
ilableJREs(ReadWorkspaceLocations.java:424)
at org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.detectD
efaultJREContaigner(ReadWorkspaceLocations.java:191)
at org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.init(Re
adWorkspaceLocations.java:89)
at org.apache.maven.plugin.eclipse.EclipsePlugin.getWorkspaceConfigurati
on(EclipsePlugin.java:1343)
at org.apache.maven.plugin.eclipse.EclipsePlugin.fillDefaultClasspathCon
tainers(EclipsePlugin.java:1092)
at org.apache.maven.plugin.eclipse.EclipsePlugin.setup(EclipsePlugin.jav
a:662)
at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractId
eSupportMojo.java:502)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:447)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:493)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:463)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[ERROR] Could not read workspace wtp server runtimes preferences : C:\dev\iplock
s\va\ipl-migrate\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclip
se.wst.server.core.prefs (The system cannot find the path specified)
[INFO] Using as WTP server : null
[INFO] Adding default classpath contaigner: org.eclipse.jdt.launching.JRE_CONTAI
NER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
[INFO] Using source status cache: C:\dev\iplocks\va\target\mvn-eclipse-cache.pro
perties
[INFO] Wrote settings to C:\dev\iplocks\va\ipl-migrate\.settings\org.eclipse.jdt
.core.prefs
[INFO] Wrote Eclipse project for "ipl-migrate" to C:\dev\iplocks\va\ipl-migrate.

On Jan 31, 2008 7:27 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi all,
>
>  We fixed a lot of issues for the version 2.5 of the eclipse plugin and
> we'll launch the vote to release it in few days.
>  In this version we improved a lot the support for RAD 6 / RAD 7 and we
> added  new features like WTP 2.0 support,  MyEclipse support,  dependencies
> to projects in your projects, ... and more.
>  You can find the complete change log here :
> http://jira.codehaus.org/browse/MECLIPSE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
>  If you want to test it before the launch of the vote you have to define
> and activate this profile :
>
>
>  apache.snapshots
>  
>
>  
>false
>  
>  
> 

Re: Two question regarding the Eclipse plugin

[nicolas de loof]

For 1), you should use   to block transitive dependencies.

For 2), any code generation plugin that runs before generate-resource phase
will get executed by mvn eclipse:eclipse and the generated source folder
added to the .classpath. If you don't get this behaviour, maybe you missuse
the plugin, or this one is not compliant with maven standards.

Nico.

2008/1/31, TM <[EMAIL PROTECTED]>:
>
>
> Hello,
>
> I'm facing two issues regarding the Maven Eclipse plugin for which I
> havn't
> found a soulution yet.
>
> 1.) Consider the simple scenario: project A depends on project B, B
> depends
> on JAR xyz. If I run mvn eclipse:eclipse for A it will add xyz to the
> classpath; so far so good. What if I want to prevent that xyz is added to
> A's classpath? Is this possible? I didn't find an option for that.
> The reason is that for complex project structures with lots of JARs and
> transitive JAR/project dependencies this will blow up the classpath with
> JAR's which are actually not referenced (if they derive from transitive
> dependencies).
> In the forum I found a "solution" that proposes to set the scope for JARs
> to
> 'optional'. But I consider this a hack and would rather prefer a switch
> like
> "addTransitiveDependenciesToClasspath=true|false" for the Eclipse plugin.
>
> 2.) I have a maven build that creates some source code (via
> jaxws-maven-plugin) which will be stored in a separate source folder (in
> order no to interfere with other source code under version control). This
> generated source code is referenced by some test code in the same project.
> Is there a possibility to add additional source folders to the Eclipse
> .classpath file when running mvn eclipse:eclipse such that I do not get
> compile errors in Eclipse, because Eclipse does not know of any other
> folders than the default ones.
>
>
> Many thanks in advance for your help,
> Thorsten
> --
> View this message in context:
> http://www.nabble.com/Two-question-regarding-the-Eclipse-plugin-tp15207989s177p15207989.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Proxied repository strategies?

[Eric Miles]

Well, part of my problem seems to stem from the fact the Cron expression
is based off the open symphony cron syntax and not unix syntax :)  I
should have noticed it was the same as continuum.

However, now I think I have a backlog of "scan jobs" that need to be
run, at least that's what it seems like is going on.  I have 4 managed
repos that get scanned every minute.  Is there any way to purge these
jobs or do I just need to let them run their course?

Thanks,
Eric
On Thu, 2008-01-31 at 10:57 -0500, Eric Miles wrote:
> All,
> 
> We have just stood up an instance of Archiva and attempting to
> incorporate it's use into our maven build processes.  However, there is
> a lack of documentation for suggested practices on how to use it.
> 
> My biggest question is surrounding proxy connector usage.  I thought it
> would be a good idea to proxy the central repository into a managed
> repository, however it seems the repository scanner is running non-stop
> now.  In over 11 hours of uptime, we have nearly a gig of logging
> information and the system is scanning this particular managed
> repository nearly non-stop.  Is this a bad idea?  Can anyone give me
> some information on repository and database scans?  I've read the
> documentation but I'm looking for a little more info.
> 
> Thanks in advance.
> 
> Eric

Two question regarding the Eclipse plugin

[TM]

Hello,

I'm facing two issues regarding the Maven Eclipse plugin for which I havn't
found a soulution yet.

1.) Consider the simple scenario: project A depends on project B, B depends
on JAR xyz. If I run mvn eclipse:eclipse for A it will add xyz to the
classpath; so far so good. What if I want to prevent that xyz is added to
A's classpath? Is this possible? I didn't find an option for that.
The reason is that for complex project structures with lots of JARs and
transitive JAR/project dependencies this will blow up the classpath with
JAR's which are actually not referenced (if they derive from transitive
dependencies).
In the forum I found a "solution" that proposes to set the scope for JARs to
'optional'. But I consider this a hack and would rather prefer a switch like
"addTransitiveDependenciesToClasspath=true|false" for the Eclipse plugin.

2.) I have a maven build that creates some source code (via
jaxws-maven-plugin) which will be stored in a separate source folder (in
order no to interfere with other source code under version control). This
generated source code is referenced by some test code in the same project.
Is there a possibility to add additional source folders to the Eclipse
.classpath file when running mvn eclipse:eclipse such that I do not get
compile errors in Eclipse, because Eclipse does not know of any other
folders than the default ones.


Many thanks in advance for your help,
Thorsten
-- 
View this message in context: 
http://www.nabble.com/Two-question-regarding-the-Eclipse-plugin-tp15207989s177p15207989.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: maven renaming jar files

[Wayne Fay]

We've had more than one person show up on this list complaining about
strange difficulties with Maven. After a bit of prodding, they tell us
that they manually created their repo and the pom files, if they exist
at all, are just GAV with no transitive deps. And then they're usually
complaining about how Maven isn't working like they expected.

I just want to make sure this happens to as few people as possible. If
you know what you're doing and want to check-in some files, please do
it, especially for things like Websphere and Weblogic that will never
appear in the Central repo.

But doing this for things like commons-* is a bad practice. Even if
you know what you're doing, you probably should not be checking in
files like these manually.

Wayne

On 1/31/08, Simon Kitching <[EMAIL PROTECTED]> wrote:
> I've certainly done something similar in the past. To reduce network traffic, 
> and to better control what libs are used, it is nice to have a repository on 
> a local server hosting the jars you need.
>
> It is very tempting to just take the set of jars you have always been using 
> (in an existing ant-based build process or similar) and just upload them to 
> that new repository. It is certainly easier than finding a maven repository 
> proxy application, and setting that up.
>
> I don't see a lot wrong with doing that - except that you do need to get the 
> group ids right!
>
> Of course long-term, having a proper repository manager installed locally 
> appears to be the right solution. Some day I have to get that organised for 
> my workplace...
>
> Interesting to see that the war plugin does detect filename clashes; as 
> discussed in another thread recently it appears that the dependency plugin 
> does not...
>
> Regards,
> Simon
>
>  Wayne Fay <[EMAIL PROTECTED]> schrieb:
> > If you're using "mvn install" or "mvn deploy" to install/deploy common
> > artifacts like commons-logging etc, then you're probably using Maven
> > wrong.
> >
> > What you've described is exactly what the problem was. You had added
> > c-l as a particular G/A/V and then c-l was coming in as a transitive
> > dep under a different G/A/V. Since the plugin detected a name
> > collision, it expanded the name to include the group as well, to make
> > it unique.
> >
> > Why did you install/deploy commons-logging instead of simply adding a
> > ? You're not the first person to report doing this, so I
> > want to understand if there is a failure in the documentation
> > somewhere or if new users are simply making poor assumptions about
> > what Maven does.
> >
> > Wayne
> >
> > On 1/31/08, amit kumar <[EMAIL PROTECTED]> wrote:
> > > I have overcome the problem. And guess know the reason for that,
> > > actually at the time of creating the LAN maven repository, I have
> > > installed common components under org.apache.commons groupId (
> > > assuming the convention of groupId as package name ). So now when I
> > > was including commons-logging as dependency in my pom.xml,
> > > what I added to pom looked like
> > >
> > > org.apache.commons
> > > commons-logging
> > > 1.1
> > >
> > > But there was another dependency in my pom.xml which as
> > > commons-logging as transitive dependency with same version, so what
> > > was happening(probably) was that maven instead of overriding the jar
> > > file was renaming it, may be because the jars were differently
> > > identified as groupId+artifactId+version.
> > > Still a little confused about my own explanation of the happenings :)
> > >
> > > Amit
> > >
> > > On Jan 30, 2008 9:51 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> > > > Looks weird.
> > > > Do you use a released version ? or the current snapshot ?
> > > >
> > > > Could you load an issue in jira with a simple project which reproduce 
> > > > this ?
> > > >
> > > > --
> > > > Olivier
> > > >
> > > > 2008/1/30, amit kumar <[EMAIL PROTECTED]>:
> > > >
> > > > > Hi,.
> > > > > When I am packaging a WAR project, I am seeing the following thing 
> > > > > happening...
> > > > >
> > > > > [DEBUG] Processing: commons-logging-1.1.jar
> > > > > [DEBUG] Duplicate found: commons-logging-1.1.jar
> > > > > [DEBUG] Renamed to: commons-logging-commons-logging-1.1.jar
> > > > >
> > > > > Any idea why this happens and how to avoid this?
> > > > > I am mentioning commons-logging-1.1 as my dependency in the pom.xml,
> > > > > and have suppressed the other versions of commons logging which were
> > > > > getting packaged as transitive dependencies of project dependencies
> > > > > using  tag in dependency taf. Same is happening with
> > > > > commons-digester and other dependencies.
> > > > >
> > > > >
> > > > > Regards,
> > > > > Amit
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > > -
> > > > To unsubs

Proxied repository strategies?

[Eric Miles]

All,

We have just stood up an instance of Archiva and attempting to
incorporate it's use into our maven build processes.  However, there is
a lack of documentation for suggested practices on how to use it.

My biggest question is surrounding proxy connector usage.  I thought it
would be a good idea to proxy the central repository into a managed
repository, however it seems the repository scanner is running non-stop
now.  In over 11 hours of uptime, we have nearly a gig of logging
information and the system is scanning this particular managed
repository nearly non-stop.  Is this a bad idea?  Can anyone give me
some information on repository and database scans?  I've read the
documentation but I'm looking for a little more info.

Thanks in advance.

Eric

Copying resources outside of the distribution archive

[Julien Martin]

Hello,

Say I have the following directory structure for my project:

myproject
--myresources/foo.sql (located within myproject directory)
--src/main/java/etc.

And I want to have the resulting directory structure:
myyproject
-target/executable/
--myproject.jar(located within executable directory)
--myresources/foo.sql

Is that possible? It seems the targetPath points to the classes directory.

Any clue welcome,

Julien.

maven-eclipse-plugin 2.5 coming soon

[Arnaud HERITIER]

Hi all,

  We fixed a lot of issues for the version 2.5 of the eclipse plugin and
we'll launch the vote to release it in few days.
  In this version we improved a lot the support for RAD 6 / RAD 7 and we
added  new features like WTP 2.0 support,  MyEclipse support,  dependencies
to projects in your projects, ... and more.
  You can find the complete change log here :
http://jira.codehaus.org/browse/MECLIPSE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
  If you want to test it before the launch of the vote you have to define
and activate this profile :


  apache.snapshots
  

  
false
  
  
  apache.snapshots
  Maven Snapshots
  http://people.apache.org/maven-snapshot-repository

  
  

  
false
  
  
  apache.plugin.snapshots
  Maven Plugin Snapshots
  http://people.apache.org/maven-snapshot-repository

  


 And then you can call this command :

  mvn org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse

(or another mojo).

The documentation of the 2.5 was previously deployed by error, thus I just
updated it to give you the new version.

Cheers,

Arnaud

-- 
..
Arnaud HERITIER
..
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...

Re: maven renaming jar files

[Simon Kitching]

I've certainly done something similar in the past. To reduce network traffic, 
and to better control what libs are used, it is nice to have a repository on a 
local server hosting the jars you need.

It is very tempting to just take the set of jars you have always been using (in 
an existing ant-based build process or similar) and just upload them to that 
new repository. It is certainly easier than finding a maven repository proxy 
application, and setting that up.

I don't see a lot wrong with doing that - except that you do need to get the 
group ids right!

Of course long-term, having a proper repository manager installed locally 
appears to be the right solution. Some day I have to get that organised for my 
workplace...

Interesting to see that the war plugin does detect filename clashes; as 
discussed in another thread recently it appears that the dependency plugin does 
not...

Regards,
Simon

 Wayne Fay <[EMAIL PROTECTED]> schrieb:
> If you're using "mvn install" or "mvn deploy" to install/deploy common
> artifacts like commons-logging etc, then you're probably using Maven
> wrong.
> 
> What you've described is exactly what the problem was. You had added
> c-l as a particular G/A/V and then c-l was coming in as a transitive
> dep under a different G/A/V. Since the plugin detected a name
> collision, it expanded the name to include the group as well, to make
> it unique.
> 
> Why did you install/deploy commons-logging instead of simply adding a
> ? You're not the first person to report doing this, so I
> want to understand if there is a failure in the documentation
> somewhere or if new users are simply making poor assumptions about
> what Maven does.
> 
> Wayne
> 
> On 1/31/08, amit kumar <[EMAIL PROTECTED]> wrote:
> > I have overcome the problem. And guess know the reason for that,
> > actually at the time of creating the LAN maven repository, I have
> > installed common components under org.apache.commons groupId (
> > assuming the convention of groupId as package name ). So now when I
> > was including commons-logging as dependency in my pom.xml,
> > what I added to pom looked like
> >
> > org.apache.commons
> > commons-logging
> > 1.1
> >
> > But there was another dependency in my pom.xml which as
> > commons-logging as transitive dependency with same version, so what
> > was happening(probably) was that maven instead of overriding the jar
> > file was renaming it, may be because the jars were differently
> > identified as groupId+artifactId+version.
> > Still a little confused about my own explanation of the happenings :)
> >
> > Amit
> >
> > On Jan 30, 2008 9:51 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> > > Looks weird.
> > > Do you use a released version ? or the current snapshot ?
> > >
> > > Could you load an issue in jira with a simple project which reproduce 
> > > this ?
> > >
> > > --
> > > Olivier
> > >
> > > 2008/1/30, amit kumar <[EMAIL PROTECTED]>:
> > >
> > > > Hi,.
> > > > When I am packaging a WAR project, I am seeing the following thing 
> > > > happening...
> > > >
> > > > [DEBUG] Processing: commons-logging-1.1.jar
> > > > [DEBUG] Duplicate found: commons-logging-1.1.jar
> > > > [DEBUG] Renamed to: commons-logging-commons-logging-1.1.jar
> > > >
> > > > Any idea why this happens and how to avoid this?
> > > > I am mentioning commons-logging-1.1 as my dependency in the pom.xml,
> > > > and have suppressed the other versions of commons logging which were
> > > > getting packaged as transitive dependencies of project dependencies
> > > > using  tag in dependency taf. Same is happening with
> > > > commons-digester and other dependencies.
> > > >
> > > >
> > > > Regards,
> > > > Amit
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


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

Filtering files from dependencySets with the assembly plugin

[Dirk Jaeckel]

Hi!

I want to extract files from a dependent artifact (foo) and filter them before I put the 
into the assembly.


Given the following pom.xml:



  4.0.0
  name.jaeckel.dirk
  assemble
  pom
  0.4-SNAPSHOT
  assemble

  

  name.jaeckel.dirk
  foo
  0.4-SNAPSHOT

  

  
mod
  

  

  
maven-assembly-plugin
2.2-beta-2-SNAPSHOT

  
build.test.properties
  
  
src/main/assembly/frontend.xml
  

  

  


the following assembly:



frontend

tar.gz



src/main/files_file_filtered.txt
true






  
name.jaeckel.dirk:mod
  
  true
  
true
  
  

  
name.jaeckel.dirk:foo
  
  true
  
true
  
  






and build.test.properties:

foo=bar


In the resulting assembly only in src/main/files_file_filtered.txt foo gets 
replaced.
The files inside name.jaeckel.dirk:foo are not filtered regardless wether the dependencySet 
inside the moduleSets or the standalone version is used. The files from 
name.jaeckel.dirk:mod are also not filtered.



1. What am I doing wrong here?
2. Which earlier Version of the plugin (<2.2-beta-2-SNAPSHOT) supports filtering? All 
versions I tried give the following error:


[INFO] Error configuring: org.apache.maven.plugins:maven-assembly-plugin. Reason: ERROR: 
Cannot override read-only parameter: filters in goal: assembly:assembly



Thanks for your help,

Dirk Jaeckel



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

Re: maven renaming jar files

[Wayne Fay]

If you're using "mvn install" or "mvn deploy" to install/deploy common
artifacts like commons-logging etc, then you're probably using Maven
wrong.

What you've described is exactly what the problem was. You had added
c-l as a particular G/A/V and then c-l was coming in as a transitive
dep under a different G/A/V. Since the plugin detected a name
collision, it expanded the name to include the group as well, to make
it unique.

Why did you install/deploy commons-logging instead of simply adding a
? You're not the first person to report doing this, so I
want to understand if there is a failure in the documentation
somewhere or if new users are simply making poor assumptions about
what Maven does.

Wayne

On 1/31/08, amit kumar <[EMAIL PROTECTED]> wrote:
> I have overcome the problem. And guess know the reason for that,
> actually at the time of creating the LAN maven repository, I have
> installed common components under org.apache.commons groupId (
> assuming the convention of groupId as package name ). So now when I
> was including commons-logging as dependency in my pom.xml,
> what I added to pom looked like
>
> org.apache.commons
> commons-logging
> 1.1
>
> But there was another dependency in my pom.xml which as
> commons-logging as transitive dependency with same version, so what
> was happening(probably) was that maven instead of overriding the jar
> file was renaming it, may be because the jars were differently
> identified as groupId+artifactId+version.
> Still a little confused about my own explanation of the happenings :)
>
> Amit
>
> On Jan 30, 2008 9:51 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> > Looks weird.
> > Do you use a released version ? or the current snapshot ?
> >
> > Could you load an issue in jira with a simple project which reproduce this ?
> >
> > --
> > Olivier
> >
> > 2008/1/30, amit kumar <[EMAIL PROTECTED]>:
> >
> > > Hi,.
> > > When I am packaging a WAR project, I am seeing the following thing 
> > > happening...
> > >
> > > [DEBUG] Processing: commons-logging-1.1.jar
> > > [DEBUG] Duplicate found: commons-logging-1.1.jar
> > > [DEBUG] Renamed to: commons-logging-commons-logging-1.1.jar
> > >
> > > Any idea why this happens and how to avoid this?
> > > I am mentioning commons-logging-1.1 as my dependency in the pom.xml,
> > > and have suppressed the other versions of commons logging which were
> > > getting packaged as transitive dependencies of project dependencies
> > > using  tag in dependency taf. Same is happening with
> > > commons-digester and other dependencies.
> > >
> > >
> > > Regards,
> > > Amit
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Problems installing maven

[Alexander Petri]

Hi, 

 

if i run "mvn" from console (i.e. mvn -version)  it gets the same output
like 

if I call "java". Does anyone know what i did wrong?

 

The Environmentpaths/Variables should be correct. Im using maven 2.0.8 and
WinVista

 

thx

Re: Dependency resolution of maven-war-plugin

[Felix Röthenbacher]

Thanks, Nick, that helped a lot.

Felix

On 01/31/2008 03:13 PM, [EMAIL PROTECTED] wrote:

Hmm, I've looked at the axis2 wsdl2code plugin and I see your
problem: the plugin is changing the dependencies. It has hardcoded
groupId/artifactId combinations and adds these to the project.

This is not a problem with the war plugin. The wsdl2code plugin
should clean up their changes or not change them at all.

Hth,

Nick Stolwijk


-Original Message- From: Felix Röthenbacher
[mailto:[EMAIL PROTECTED] Sent: Thu 1/31/2008 3:01 PM To: Maven
Users List Subject: Re: Dependency resolution of maven-war-plugin

I'm using Maven 2.0.8 with maven-war-plugin version
2.1-alpha-2-SNAPSHOT.

The dependency is added although I specified an exclusion in the
pom.xml (see below):

pom.xml:

   org.apache.axis2 
axis2-wsdl2code-maven-plugin  
...
org.apache.axis2 
axis2-xmlbeans 
${axis2.version}   
xmlbeans xbean 
 
 


Executing maven with the -X switch set the following debug messages 
are produced indicating that the dependency on xmlbeans:xbean is

already on the classpath for compiler:compile, etc. The
axis2-wsdl2code plugin seems to add this dependency though specified
as an exclusion.

... [INFO] [axis2-wsdl2code:wsdl2code {execution: publisher-wsdl}] 
... [DEBUG] The artifact org.apache.ws.commons.axiom:axiom-api is

already present  in the project and will not be added. [DEBUG] The
artifact org.apache.ws.commons.axiom:axiom-impl is already present
in the project and will not be added. [DEBUG] The artifact
commons-httpclient:commons-httpclient is already present  in the
project and will not be added. [DEBUG] The artifact wsdl4j:wsdl4j is
already present  in the project and will not be added. [DEBUG] Adding
artifact org.apache.axis2:axis2-xmlbeans [DEBUG] Adding artifact
xmlbeans:xbean [DEBUG] The projects dependency artifacts are: [DEBUG]
com.sun.facelets:jsf-facelets:1.1.13:null:compile:jar [DEBUG]
xmlbeans:xbean:2.2.0:null:compile:jar ... ... [INFO]
[compiler:testCompile] [DEBUG] Using compiler 'javac'. [DEBUG]
Classpath: [ ... 
/home/felix/.m2/repository/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar ...] 
... ... [DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-surefire-plugin:2.4.1-SNAPSHOT:test'
--> ... [DEBUG]   (f) classpathElements = [ ... 
/home/felix/.m2/repository/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar, ...
] ... [DEBUG]   (f) projectArtifactMap = { ... 
xmlbeans:xbean=xmlbeans:xbean:jar:2.2.0:compile, ... } ... [DEBUG]

Test Classpath : [DEBUG]
/home/felix/.m2/repository/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar ... 
...


Finally the maven-war-module adds this plugin transitive dependency
also:

[INFO] [war:war] [INFO] Packaging webapp [INFO] Assembling
webapp[publisher-webapp] in 
[/home/felix/dev/lwp/publisher/publisher-webapp/target/publisher-webapp-1.0.0-SNAPSHOT]

 [INFO] Processing war project ... [DEBUG] Processing:
xbean-2.2.0.jar [DEBUG]  * WEB-INF/lib/xbean-2.2.0.jar is up to date.
 ... [INFO] Webapp assembled in[1437 msecs] [INFO] Building war: 
/home/felix/dev/lwp/publisher/publisher-webapp/target/publisher-webapp-1.0.0-SNAPSHOT.war

 ... [DEBUG] adding entry WEB-INF/lib/xbean-2.2.0.jar

Any Ideas?

Felix


On 01/31/2008 12:03 PM, [EMAIL PROTECTED] wrote:

This is the first time I see that a plugin transitive dependency
makes it into the final artifact. What versions of maven and the
maven-war-plugin are you using? With regards,

Nick Stolwijk

-Original Message- From: amit kumar
[mailto:[EMAIL PROTECTED] Sent: Thu 1/31/2008 11:56 AM To:
Maven Users List Subject: Re: Dependency resolution of
maven-war-plugin

Yes Felix maven-war-plugin does include the transitive
dependencies. For a transitive dependency of a plugin, the
way(workaround) I found and using is to declare that dependency
explicitly in your pom.xml and declare it to be available at only
compile time (  tag).

For the transitive dependencies of the rest of the dependencies I
am using  tag with in the dependency tag. That probably
be not the sanest way of it, but this was what I could find out
with the help of other maven users here on the list.

Amit

On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]>
wrote:

Hello

I have a question re dependency resolution of the
maven-war-plugin. If I run 'mvn install' a war is built including
the library xbeans.jar (xmlbeans:xbean is a transitive dependency
of a plugin). Why is this dependency included though not
declared?

A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean'
returns with no result. It seems to me that maven-war-plugin
includes also transitive plugin dependencies.

Thanks for your help, Felix








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

Re: problems with multiple profiles...

[supareno]

Hmm, I don't know why your first example is working, because that is not a 
valid layout for the POM. See [1].
  

because eclipse plugin accept this layout
i tried my pom.xml with " mvn help:active-profiles " with a terminal and 
i had an error

Could you give us the output of mvn -e -P  
  

i found the problem:
i have got a build tag with sourceDirectory tag outside the profile !

with the following layout, i don't have any error


   [...]
   
  ...
  src/test
  
   
   true
   src/main/resources/
   
  foo
   
   
  
   
   [...]
   
  
 
  [...]
 
  
  
 

  [...]
 
  
   


With regards,

Nick Stolwijk

[1] http://maven.apache.org/ref/2.0.7/maven-model/maven.html
  

thanks a lot

supareno

-Original Message-
From: supareno [mailto:[EMAIL PROTECTED]
Sent: Thu 1/31/2008 2:34 PM
To: Maven Users List
Subject: problems with multiple profiles...
 
hello,


i read a lot about profiles ans i 'm stuck on a problem
i'm using eclipse 3.2
my maven version is :
Maven version: 2.0.8
my java version is:
Java version: 1.6.0_03

so, in my pom.xml, i have a profile with build, plugins and depedencies 
like this:



4.0.0
groupid
artifactid
[...]

   
  [...]
   
   
  [...]
   
   [...]



when i run this pom with the eclipse external tools launcher, everything 
works fine

but i put mu profile between  tag like this


[...]


   [...]




to add another profile, i've got an error which is:

INFO] 


[ERROR] BUILD FAILURE
[INFO] 

[INFO] Error scanning for extensions: Error building model lineage in 
order to pre-scan for extensions: Failed to parse model from: 
/home//pom.xml for project unknown at /home//pom.xml
[INFO] 


[INFO] Total time: 1 second
[INFO] Finished at: Thu Jan 31 14:23:32 CET 2008
[INFO] Memory 2M/4M
[INFO] 



what's wrong with my config??

regards
supareno

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



  



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

RE: Dependency resolution of maven-war-plugin

[nicklist]

Hmm, I've looked at the axis2 wsdl2code plugin and I see your problem: the 
plugin is changing the dependencies. It has hardcoded groupId/artifactId 
combinations and adds these to the project.

This is not a problem with the war plugin. The wsdl2code plugin should clean up 
their changes or not change them at all.

Hth,

Nick Stolwijk


-Original Message-
From: Felix Röthenbacher [mailto:[EMAIL PROTECTED]
Sent: Thu 1/31/2008 3:01 PM
To: Maven Users List
Subject: Re: Dependency resolution of maven-war-plugin
 
I'm using Maven 2.0.8 with maven-war-plugin version 2.1-alpha-2-SNAPSHOT.

The dependency is added although I specified an
exclusion in the pom.xml (see below):

pom.xml:

   
 
   
 org.apache.axis2
 axis2-wsdl2code-maven-plugin
 
   ...
 
 
   
 org.apache.axis2
 axis2-xmlbeans
 ${axis2.version}
 
   
 xmlbeans
 xbean
   
 
   
 
   
 
   

Executing maven with the -X switch set the following debug messages
are produced indicating that the dependency on xmlbeans:xbean
is already on the classpath for compiler:compile, etc.
The axis2-wsdl2code plugin seems to add this dependency though
specified as an exclusion.

...
[INFO] [axis2-wsdl2code:wsdl2code {execution: publisher-wsdl}]
...
[DEBUG] The artifact org.apache.ws.commons.axiom:axiom-api is already 
present  in the project and will not be added.
[DEBUG] The artifact org.apache.ws.commons.axiom:axiom-impl is already 
present  in the project and will not be added.
[DEBUG] The artifact commons-httpclient:commons-httpclient is already 
present  in the project and will not be added.
[DEBUG] The artifact wsdl4j:wsdl4j is already present  in the project 
and will not be added.
[DEBUG] Adding artifact org.apache.axis2:axis2-xmlbeans
[DEBUG] Adding artifact xmlbeans:xbean
[DEBUG] The projects dependency artifacts are:
[DEBUG] com.sun.facelets:jsf-facelets:1.1.13:null:compile:jar
[DEBUG] xmlbeans:xbean:2.2.0:null:compile:jar
...
...
[INFO] [compiler:testCompile]
[DEBUG] Using compiler 'javac'.
[DEBUG] Classpath: [ ...
   /home/felix/.m2/repository/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar
   ...]
...
...
[DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-surefire-plugin:2.4.1-SNAPSHOT:test' -->
...
[DEBUG]   (f) classpathElements = [ ... 
/home/felix/.m2/repository/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar, ... ]
...
[DEBUG]   (f) projectArtifactMap = { ... 
xmlbeans:xbean=xmlbeans:xbean:jar:2.2.0:compile, ... }
...
[DEBUG] Test Classpath :
[DEBUG]   /home/felix/.m2/repository/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar
...
...

Finally the maven-war-module adds this plugin transitive dependency also:

[INFO] [war:war]
[INFO] Packaging webapp
[INFO] Assembling webapp[publisher-webapp] in 
[/home/felix/dev/lwp/publisher/publisher-webapp/target/publisher-webapp-1.0.0-SNAPSHOT]
[INFO] Processing war project
...
[DEBUG] Processing: xbean-2.2.0.jar
[DEBUG]  * WEB-INF/lib/xbean-2.2.0.jar is up to date.
...
[INFO] Webapp assembled in[1437 msecs]
[INFO] Building war: 
/home/felix/dev/lwp/publisher/publisher-webapp/target/publisher-webapp-1.0.0-SNAPSHOT.war
...
[DEBUG] adding entry WEB-INF/lib/xbean-2.2.0.jar

Any Ideas?

Felix


On 01/31/2008 12:03 PM, [EMAIL PROTECTED] wrote:
> This is the first time I see that a plugin transitive dependency makes it 
> into the final
 > artifact. What versions of maven and the maven-war-plugin are you using?
> 
> With regards,
> 
> Nick Stolwijk
> 
> -Original Message-
> From: amit kumar [mailto:[EMAIL PROTECTED]
> Sent: Thu 1/31/2008 11:56 AM
> To: Maven Users List
> Subject: Re: Dependency resolution of maven-war-plugin
>  
> Yes Felix maven-war-plugin does include the transitive dependencies.
> For a transitive dependency of a plugin, the way(workaround) I found
> and using is to declare that dependency explicitly in your pom.xml and
> declare it to be available at only compile time (  tag).
> 
> For the transitive dependencies of the rest of the dependencies I am
> using  tag with in the dependency tag. That probably be not
> the sanest way of it, but this was what I could find out with the help
> of other maven users here on the list.
> 
> Amit
> 
> On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote:
>> Hello
>>
>> I have a question re dependency resolution of the maven-war-plugin.
>> If I run 'mvn install' a war is built including the library xbeans.jar
>> (xmlbeans:xbean is a transitive dependency of a plugin). Why is this
>> dependency included though not declared?
>>
>> A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns
>> with no result. It seems to me that maven-war-plugin includes also
>> transitive plugin dependencies.
>>
>> Thanks for your help, Felix
>>
>>



-
To unsubscribe, e-mail: [EMAIL PROTEC

Re: Dependency resolution of maven-war-plugin

[Felix Röthenbacher]

I'm using Maven 2.0.8 with maven-war-plugin version 2.1-alpha-2-SNAPSHOT.

The dependency is added although I specified an
exclusion in the pom.xml (see below):

pom.xml:

  

  
org.apache.axis2
axis2-wsdl2code-maven-plugin

  ...


  
org.apache.axis2
axis2-xmlbeans
${axis2.version}

  
xmlbeans
xbean
  

  

  

  

Executing maven with the -X switch set the following debug messages
are produced indicating that the dependency on xmlbeans:xbean
is already on the classpath for compiler:compile, etc.
The axis2-wsdl2code plugin seems to add this dependency though
specified as an exclusion.

...
[INFO] [axis2-wsdl2code:wsdl2code {execution: publisher-wsdl}]
...
[DEBUG] The artifact org.apache.ws.commons.axiom:axiom-api is already 
present  in the project and will not be added.
[DEBUG] The artifact org.apache.ws.commons.axiom:axiom-impl is already 
present  in the project and will not be added.
[DEBUG] The artifact commons-httpclient:commons-httpclient is already 
present  in the project and will not be added.
[DEBUG] The artifact wsdl4j:wsdl4j is already present  in the project 
and will not be added.

[DEBUG] Adding artifact org.apache.axis2:axis2-xmlbeans
[DEBUG] Adding artifact xmlbeans:xbean
[DEBUG] The projects dependency artifacts are:
[DEBUG] com.sun.facelets:jsf-facelets:1.1.13:null:compile:jar
[DEBUG] xmlbeans:xbean:2.2.0:null:compile:jar
...
...
[INFO] [compiler:testCompile]
[DEBUG] Using compiler 'javac'.
[DEBUG] Classpath: [ ...
  /home/felix/.m2/repository/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar
  ...]
...
...
[DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-surefire-plugin:2.4.1-SNAPSHOT:test' -->

...
[DEBUG]   (f) classpathElements = [ ... 
/home/felix/.m2/repository/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar, ... ]

...
[DEBUG]   (f) projectArtifactMap = { ... 
xmlbeans:xbean=xmlbeans:xbean:jar:2.2.0:compile, ... }

...
[DEBUG] Test Classpath :
[DEBUG]   /home/felix/.m2/repository/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar
...
...

Finally the maven-war-module adds this plugin transitive dependency also:

[INFO] [war:war]
[INFO] Packaging webapp
[INFO] Assembling webapp[publisher-webapp] in 
[/home/felix/dev/lwp/publisher/publisher-webapp/target/publisher-webapp-1.0.0-SNAPSHOT]

[INFO] Processing war project
...
[DEBUG] Processing: xbean-2.2.0.jar
[DEBUG]  * WEB-INF/lib/xbean-2.2.0.jar is up to date.
...
[INFO] Webapp assembled in[1437 msecs]
[INFO] Building war: 
/home/felix/dev/lwp/publisher/publisher-webapp/target/publisher-webapp-1.0.0-SNAPSHOT.war

...
[DEBUG] adding entry WEB-INF/lib/xbean-2.2.0.jar

Any Ideas?

Felix


On 01/31/2008 12:03 PM, [EMAIL PROTECTED] wrote:

This is the first time I see that a plugin transitive dependency makes it into 
the final

> artifact. What versions of maven and the maven-war-plugin are you using?


With regards,

Nick Stolwijk

-Original Message-
From: amit kumar [mailto:[EMAIL PROTECTED]
Sent: Thu 1/31/2008 11:56 AM
To: Maven Users List
Subject: Re: Dependency resolution of maven-war-plugin
 
Yes Felix maven-war-plugin does include the transitive dependencies.

For a transitive dependency of a plugin, the way(workaround) I found
and using is to declare that dependency explicitly in your pom.xml and
declare it to be available at only compile time (  tag).

For the transitive dependencies of the rest of the dependencies I am
using  tag with in the dependency tag. That probably be not
the sanest way of it, but this was what I could find out with the help
of other maven users here on the list.

Amit

On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote:

Hello

I have a question re dependency resolution of the maven-war-plugin.
If I run 'mvn install' a war is built including the library xbeans.jar
(xmlbeans:xbean is a transitive dependency of a plugin). Why is this
dependency included though not declared?

A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns
with no result. It seems to me that maven-war-plugin includes also
transitive plugin dependencies.

Thanks for your help, Felix






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

RE: Checkstyle Problem

[Mitesh51]

Thank you Very much.

Things worked.

I will be grateful to u for ur help.


nicklist wrote:
> 
> Please throw away the first, the goal jar:install is not valid.
> 
> If you use the second, with my configuration it should work.
> 
> Hth,
> 
> Nick Stolwijk
> 
> -Original Message-
> From: Mitesh51 [mailto:[EMAIL PROTECTED]
> Sent: Thu 1/31/2008 12:07 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Checkstyle Problem
>  
> 
> in Continuum-> Bulild Defination Template, There are 2 Goals 
> 
> clean:clean jar:install
> 
> clean install
> 
> 
> MATHUS Baptiste wrote:
>> 
>> Hi,
>> 
>> If you need something urgently as you say, better would be to try to
>> answer questions asked by those who try to help you :-). 
>> 
>> *What goal did you configure inside Continuum for your project ?*
>> 
>> To generate the reports, you have to use "mvn site" at least. If not, the
>> site, and so the integrated reports won't be generated.
>> 
>> Cheers.
>> 
>> -Message d'origine-
>> De : Mitesh51 [mailto:[EMAIL PROTECTED] 
>> Envoyé : jeudi 31 janvier 2008 11:40
>> À : [EMAIL PROTECTED]
>> Objet : RE: Checkstyle Problem
>> 
>> 
>> What i want to do is generate a checkstyle report.
>> 
>> I can do thais via mvn checkstyle:checkstyle from command prompt but i am
>> not able to generate that report when i use the continumm to run the
>> Maven
>> project.
>> 
>> If u have yahoo id then can u give me?
>> 
>> Please I need the solution very urgently. 
>> 
>> 
>> nicklist wrote:
>>> 
>>> What goals or phase are you running from Continuum? The reporting 
>>> section is only used when generating a site (thus, running mvn site) 
>>> and not when running an install or deploy.
>>> 
>>> Hth,
>>> 
>>> Nick Stolwijk
>>> 
>>> ps. I don't think you need the checkstyle artifact as dependency. This 
>>> way it will be included in your project.
>>> 
>>> 
>>> -Original Message-
>>> From: Mitesh51 [mailto:[EMAIL PROTECTED]
>>> Sent: Thu 1/31/2008 11:07 AM
>>> To: [EMAIL PROTECTED]
>>> Subject: Checkstyle Problem
>>>  
>>> 
>>> I want to use checkstyle plugin and use it in continuum.
>>> 
>>> My pom.xml looks like .
>>> 
>>> http://maven.apache.org/POM/4.0.0";
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>>> http://maven.apache.org/maven-v4_0_0.xsd";>
>>>   4.0.0
>>>   com.mycompany.app
>>>   my-app
>>>   jar
>>>   1.0-SNAPSHOT
>>>   my-app
>>>   http://maven.apache.org
>>> 
>>> 
>>> 
>>> scm:svn:svn://shikhas:[EMAIL 
>>> PROTECTED]/iLabsDevRepo/Source/trunk/iTraining/trunk/maven/my-app/
>>> 
>>> 
>>> 
>>>   
>>>
>>>   checkstyle
>>>   checkstyle
>>>   4.1
>>>   jar
>>>   package
>>>   true
>>> 
>>> 
>>>   
>>> 
>>>  
>>>  
>>> 
>>>
>>> org.apache.maven.plugins
>>>
>>> maven-checkstyle-plugin 
>>>  
>>> D:\ILabs 
>>> Task\Maven\checkstyle-4.4\sun_checks.xml
>>>  
>>>  
>>>  
>>> 
>>> 
>>> 
>>> 
>>> It is downloading the jars necessary for the checkstyle but it is not 
>>> generating the checkstyle documents.
>>> 
>>> Is there anything missing in pom.xml?
>>> 
>>> After running the build script in continuum, It does not generate the 
>>> checkstyle reports in the Output directory with the use of continuum.
>>> 
>>> Any Suggestions??
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Checkstyle-Problem-tp15201303p15201303.html
>>> Sent from the Continuum - Users mailing list archive at Nabble.com.
>>> 
>>> 
>>> 
>>> 
>> 
>> --
>> View this message in context:
>> http://www.nabble.com/Checkstyle-Problem-tp15201303p15201976.html
>> Sent from the Continuum - Users mailing list archive at Nabble.com.
>> 
>> 
> 
> -- 
> View this message in context:
> http://www.nabble.com/Checkstyle-Problem-tp15201303p15202330.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Checkstyle-Problem-tp15201303p15205211.html
Sent from the Continuum - Users mailing list archive at Nabble.com.

RE: problems with multiple profiles...

[nicklist]

Hmm, I don't know why your first example is working, because that is not a 
valid layout for the POM. See [1].

Could you give us the output of mvn -e -P  

With regards,

Nick Stolwijk

[1] http://maven.apache.org/ref/2.0.7/maven-model/maven.html

-Original Message-
From: supareno [mailto:[EMAIL PROTECTED]
Sent: Thu 1/31/2008 2:34 PM
To: Maven Users List
Subject: problems with multiple profiles...
 
hello,

i read a lot about profiles ans i 'm stuck on a problem
i'm using eclipse 3.2
my maven version is :
Maven version: 2.0.8
my java version is:
Java version: 1.6.0_03

so, in my pom.xml, i have a profile with build, plugins and depedencies 
like this:


4.0.0
groupid
artifactid
[...]

   
  [...]
   
   
  [...]
   
   [...]



when i run this pom with the eclipse external tools launcher, everything 
works fine
but i put mu profile between  tag like this


[...]


   [...]




to add another profile, i've got an error which is:

INFO] 

[ERROR] BUILD FAILURE
[INFO] 

[INFO] Error scanning for extensions: Error building model lineage in 
order to pre-scan for extensions: Failed to parse model from: 
/home//pom.xml for project unknown at /home//pom.xml
[INFO] 

[INFO] Total time: 1 second
[INFO] Finished at: Thu Jan 31 14:23:32 CET 2008
[INFO] Memory 2M/4M
[INFO] 


what's wrong with my config??

regards
supareno

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

problems with multiple profiles...

[supareno]

hello,

i read a lot about profiles ans i 'm stuck on a problem
i'm using eclipse 3.2
my maven version is :
Maven version: 2.0.8
my java version is:
Java version: 1.6.0_03

so, in my pom.xml, i have a profile with build, plugins and depedencies 
like this:



   4.0.0
   groupid
   artifactid
   [...]
   
  
 [...]
  
  
 [...]
  
  [...]
   


when i run this pom with the eclipse external tools launcher, everything 
works fine

but i put mu profile between  tag like this


   [...]
   
   
  [...]
   
   


to add another profile, i've got an error which is:

INFO] 


[ERROR] BUILD FAILURE
[INFO] 

[INFO] Error scanning for extensions: Error building model lineage in 
order to pre-scan for extensions: Failed to parse model from: 
/home//pom.xml for project unknown at /home//pom.xml
[INFO] 


[INFO] Total time: 1 second
[INFO] Finished at: Thu Jan 31 14:23:32 CET 2008
[INFO] Memory 2M/4M
[INFO] 



what's wrong with my config??

regards
supareno

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

Re: Using maven-surefire-report-plugin

[Arnaud Bailly]

Anyone ? Is this so obvious nobody cares to answer :) ? 

Cheers,
-- 
Arnaud Bailly, PhD
OQube - Software Engineering
http://www.oqube.com

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

Re: Clearcase Snapshot View Synchronisation

[Erez Nahir]

"If using dynamic views, don't you run into the potential risk of the
view contents being updated in the middle of a build?"

We have a "build oriented stream/branch" so, what we do is:
1. Monitor integration stream (we use cruisecontrol for taht)
2. Once found modification - deliver (if using UCM) or merge to the "build
stream/branch"
3. Run the build on the build stream.

That works perfect (of course, no one use the "build stream/branch" it is
only used by the build machine.

Erez.



On Jan 31, 2008 11:09 AM, Jan Fredrik Wedén <[EMAIL PROTECTED]> wrote:

> On Jan 25, 2008 6:25 PM, Kalle Korhonen <[EMAIL PROTECTED]>
> wrote:
> > Same here, dynamic views with Continuum as a build server. There were
> some
> > quirks making it play nice with ClearCase, but generally works ok (and
> yes,
> > svn is way superior).
> >
> > Kalle
> >
>
> If using dynamic views, don't you run into the potential risk of the
> view contents being updated in the middle of a build?
>
> As for the original question: we solved a similar issue using
> CruiseControl's composite builder and then running some ClearCase
> operations using an Ant script before we kicked off the Maven build.
>
> --
> - Jan Fredrik Wedén
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: Maven2 and artifact versions

[Jörg Schaible]

Simon Kitching wrote:
>  "Jörg Schaible" <[EMAIL PROTECTED]> schrieb:
>> Simon Kitching wrote:
>> 
>> [snip]
>> 
>>> Personally, I prefer the second because it is clear to all
>>> readers that yes a version *is* being specified for this
>>> dependency. With the dependencyManagement approach, it isn't
>>> clear unless you check the parent pom. However I appear to be
>>> in the minority, with many people preferring dependencyManagement.
>> 
>> Because the dependencyManagement also define the version of
> the transitive deps (at least it should since M206).
> 
> Good point. Using the $foo approach only
> works for direct dependencies; it cannot be used to influence
> the selected version for a transitive dependency.
> 
> However if you want dependencyManagement to apply to
> transient deps, you would really need to use [x.y] or
> [x.y,z.a] version numbers, right?

No, not necessarily, but yes, it depends how the accessed artifacts define 
their dependencies. As long as no locked versions are used, it will work.

> If a pom has a dependencyManagement declaration of
>   1.0
> but some required lib declares a dependency on the same artifact using
>[1.2,1.4]
> then what will happen?
> 
> I presume that version 1.2 will be used, ie the
> dependencyManagement declaration is ignored. If that is true,
> then it cannot actually be relied on unless
> dependencyManagement uses explicitly locked versions (or ranges).

Not sure about this (did not try), but AFAICS Maven bails out, since it cannot 
resolve the artifact to any version.

I think the situation is different building libraries of a framework or a 
project anyway. In a project you will probably use a project POM with locked 
versions, while for something like Commons it does not make too much sence. 
Here every component should define the versions of its deps and probably use 
version ranges only if it is known that some version is not running with it. 
However, version ranges seem not to be the most stable feature in M2 currently.

- Jörg

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

Re: Parent project version

[Stephen Connolly]

Yep!

which was why I had only  which would force you to check out
the parent.

i.e. it would be a child that _cannot_ be build without the parent, for use
by developers

the release plugin would (on the version tagged for release) replace the
 tag with the released parent's identification triplet (or
quartet if you're mad and have a classifier too) so that releasing the
parent will give a stand-alone module that can build on it's own,

but the trunk poms would not change

On Jan 30, 2008 9:19 AM, Heinrich Nirschl <[EMAIL PROTECTED]>
wrote:

> On Jan 30, 2008 8:59 AM, Erez Nahir <[EMAIL PROTECTED]> wrote:
> > I also think as Stephen,
> >
> > Having an option to specify parent with relative path will be very
> helpfull,
> > I'm sure a solution can be found to provide this functionality.
> > Maybe something like having both  and  and give
> > precedence to  such that if it is found, it will be used
> and
> > if not, the  will be used instead...
> >
> > Erez.
>
> This would give different results when the whole tree is checked out
> vs. just the module is checked out.
>
> - Henry
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: want to save in one folder all dependency jars?

[Simon Kitching]

 "Krastev schrieb:
> Hi all,
> please could you tell me is there a maven command which allows you to
> save in a predefined folder all POM dependency jars?
> say something like:
> mvn -xxx C:\temp

See the documentation for the dependency plugin:

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

Regards,
Simon

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

Maven Ant Tasks: Configured repository not available

[Thomas Tardy]

Hi all,

I'm trying to load an existing pom.xml with ant. The pom refers his parent,
which is not in the local repository. The remote repository is configured in
the settings.xml ${user.home}/.m2/settings.xml and it's working with
"normal" maven. The maven ant tasks are not able to download the parent from
the repository. I get a validation error. When I download the parent pom to
the local repository the validation is successful. After the validation
phase, the maven ant tasks are able to download artefacts from the remote
repository.

Is this a bug? What am I doing wrong?

Thank you for your help!

Regards,
Thomas

maven-release-plugin error

[Matthew Tordoff]

Hi all,

I am having difficulties with the maven-release-plugin. It is the first time I 
have attempted to use this plugin and the error that it is throwing is really 
confusing me (see below). I have setup the tagBase and developerConnection 
configuration properties within the POM. Does anyone know of a good tutorial 
for getting a release up and running, because the documentation on the plugin 
page seems light to say the least.

I tried doing the release with the version set to both trunk-SNAPSHOT-devname 
and 0.3, but this didn't seem to make any difference.

Kind Regards,

Matt


[INFO] [release:prepare]
[INFO] 

[ERROR] 
BUILD FAILURE
[INFO] 

[INFO] 
You don't have a SNAPSHOT project in the reactor projects list.
[INFO] 

[INFO] 
For more information, run Maven with the -e switch
[INFO] 

[INFO] 
Total time: 3 seconds
[INFO] Finished at: Thu Jan 31 12:07:34 GMT 
2008
[INFO] Final Memory: 5M/9M
[INFO] 

_
Free games, great prizes - get gaming at Gamesbox. 
http://www.searchgamesbox.com

want to save in one folder all dependency jars?

[Krastev, Velislav]

Hi all,
please could you tell me is there a maven command which allows you to
save in a predefined folder all POM dependency jars?
say something like:
mvn -xxx C:\temp

Thank you in advance
Regards

Krastev

Re: Dependency resolution of maven-war-plugin

[amit kumar]

regexp-1.3.jar was getting packaged with the final war. as a
dependency of buildnumber plugin



On Jan 31, 2008 4:40 PM, amit kumar <[EMAIL PROTECTED]> wrote:
> maven-war-plugin's 2.1-alpha-1 version.
> and maven  2.0.7
>
> One of the buildnumber-maven-plugin's dependency was getting packaged
> unless I put it explicitly and made it available at compile time.
>
>
> On Jan 31, 2008 4:33 PM,  <[EMAIL PROTECTED]> wrote:
> > This is the first time I see that a plugin transitive dependency makes it 
> > into the final artifact. What versions of maven and the maven-war-plugin 
> > are you using?
> >
> > With regards,
> >
> > Nick Stolwijk
> >
> >
> > -Original Message-
> > From: amit kumar [mailto:[EMAIL PROTECTED]
> > Sent: Thu 1/31/2008 11:56 AM
> > To: Maven Users List
> > Subject: Re: Dependency resolution of maven-war-plugin
> >
> > Yes Felix maven-war-plugin does include the transitive dependencies.
> > For a transitive dependency of a plugin, the way(workaround) I found
> > and using is to declare that dependency explicitly in your pom.xml and
> > declare it to be available at only compile time (  tag).
> >
> > For the transitive dependencies of the rest of the dependencies I am
> > using  tag with in the dependency tag. That probably be not
> > the sanest way of it, but this was what I could find out with the help
> > of other maven users here on the list.
> >
> > Amit
> >
> > On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote:
> > > Hello
> > >
> > > I have a question re dependency resolution of the maven-war-plugin.
> > > If I run 'mvn install' a war is built including the library xbeans.jar
> > > (xmlbeans:xbean is a transitive dependency of a plugin). Why is this
> > > dependency included though not declared?
> > >
> > > A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns
> > > with no result. It seems to me that maven-war-plugin includes also
> > > transitive plugin dependencies.
> > >
> > > Thanks for your help, Felix
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>

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

Re: Dependency resolution of maven-war-plugin

[amit kumar]

maven-war-plugin's 2.1-alpha-1 version.
and maven  2.0.7

One of the buildnumber-maven-plugin's dependency was getting packaged
unless I put it explicitly and made it available at compile time.

On Jan 31, 2008 4:33 PM,  <[EMAIL PROTECTED]> wrote:
> This is the first time I see that a plugin transitive dependency makes it 
> into the final artifact. What versions of maven and the maven-war-plugin are 
> you using?
>
> With regards,
>
> Nick Stolwijk
>
>
> -Original Message-
> From: amit kumar [mailto:[EMAIL PROTECTED]
> Sent: Thu 1/31/2008 11:56 AM
> To: Maven Users List
> Subject: Re: Dependency resolution of maven-war-plugin
>
> Yes Felix maven-war-plugin does include the transitive dependencies.
> For a transitive dependency of a plugin, the way(workaround) I found
> and using is to declare that dependency explicitly in your pom.xml and
> declare it to be available at only compile time (  tag).
>
> For the transitive dependencies of the rest of the dependencies I am
> using  tag with in the dependency tag. That probably be not
> the sanest way of it, but this was what I could find out with the help
> of other maven users here on the list.
>
> Amit
>
> On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote:
> > Hello
> >
> > I have a question re dependency resolution of the maven-war-plugin.
> > If I run 'mvn install' a war is built including the library xbeans.jar
> > (xmlbeans:xbean is a transitive dependency of a plugin). Why is this
> > dependency included though not declared?
> >
> > A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns
> > with no result. It seems to me that maven-war-plugin includes also
> > transitive plugin dependencies.
> >
> > Thanks for your help, Felix
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

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

RE: Checkstyle Problem

[Mitesh51]

in Continuum-> Bulild Defination Template, There are 2 Goals 

clean:clean jar:install

clean install


MATHUS Baptiste wrote:
> 
> Hi,
> 
> If you need something urgently as you say, better would be to try to
> answer questions asked by those who try to help you :-). 
> 
> *What goal did you configure inside Continuum for your project ?*
> 
> To generate the reports, you have to use "mvn site" at least. If not, the
> site, and so the integrated reports won't be generated.
> 
> Cheers.
> 
> -Message d'origine-
> De : Mitesh51 [mailto:[EMAIL PROTECTED] 
> Envoyé : jeudi 31 janvier 2008 11:40
> À : [EMAIL PROTECTED]
> Objet : RE: Checkstyle Problem
> 
> 
> What i want to do is generate a checkstyle report.
> 
> I can do thais via mvn checkstyle:checkstyle from command prompt but i am
> not able to generate that report when i use the continumm to run the Maven
> project.
> 
> If u have yahoo id then can u give me?
> 
> Please I need the solution very urgently. 
> 
> 
> nicklist wrote:
>> 
>> What goals or phase are you running from Continuum? The reporting 
>> section is only used when generating a site (thus, running mvn site) 
>> and not when running an install or deploy.
>> 
>> Hth,
>> 
>> Nick Stolwijk
>> 
>> ps. I don't think you need the checkstyle artifact as dependency. This 
>> way it will be included in your project.
>> 
>> 
>> -Original Message-
>> From: Mitesh51 [mailto:[EMAIL PROTECTED]
>> Sent: Thu 1/31/2008 11:07 AM
>> To: [EMAIL PROTECTED]
>> Subject: Checkstyle Problem
>>  
>> 
>> I want to use checkstyle plugin and use it in continuum.
>> 
>> My pom.xml looks like .
>> 
>> http://maven.apache.org/POM/4.0.0";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>> http://maven.apache.org/maven-v4_0_0.xsd";>
>>   4.0.0
>>   com.mycompany.app
>>   my-app
>>   jar
>>   1.0-SNAPSHOT
>>   my-app
>>   http://maven.apache.org
>> 
>>  
>> 
>> scm:svn:svn://shikhas:[EMAIL 
>> PROTECTED]/iLabsDevRepo/Source/trunk/iTraining/trunk/maven/my-app/
>>  
>> 
>> 
>>   
>>
>>   checkstyle
>>   checkstyle
>>   4.1
>>jar
>>   package
>>true
>> 
>> 
>>   
>> 
>>   
>>  
>> 
>>
>> org.apache.maven.plugins
>>
>> maven-checkstyle-plugin 
>>  
>> D:\ILabs 
>> Task\Maven\checkstyle-4.4\sun_checks.xml
>>  
>>  
>>  
>> 
>> 
>> 
>> 
>> It is downloading the jars necessary for the checkstyle but it is not 
>> generating the checkstyle documents.
>> 
>> Is there anything missing in pom.xml?
>> 
>> After running the build script in continuum, It does not generate the 
>> checkstyle reports in the Output directory with the use of continuum.
>> 
>> Any Suggestions??
>> --
>> View this message in context:
>> http://www.nabble.com/Checkstyle-Problem-tp15201303p15201303.html
>> Sent from the Continuum - Users mailing list archive at Nabble.com.
>> 
>> 
>> 
>> 
> 
> --
> View this message in context:
> http://www.nabble.com/Checkstyle-Problem-tp15201303p15201976.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Checkstyle-Problem-tp15201303p15202330.html
Sent from the Continuum - Users mailing list archive at Nabble.com.

RE: Dependency resolution of maven-war-plugin

[nicklist]

This is the first time I see that a plugin transitive dependency makes it into 
the final artifact. What versions of maven and the maven-war-plugin are you 
using?

With regards,

Nick Stolwijk

-Original Message-
From: amit kumar [mailto:[EMAIL PROTECTED]
Sent: Thu 1/31/2008 11:56 AM
To: Maven Users List
Subject: Re: Dependency resolution of maven-war-plugin
 
Yes Felix maven-war-plugin does include the transitive dependencies.
For a transitive dependency of a plugin, the way(workaround) I found
and using is to declare that dependency explicitly in your pom.xml and
declare it to be available at only compile time (  tag).

For the transitive dependencies of the rest of the dependencies I am
using  tag with in the dependency tag. That probably be not
the sanest way of it, but this was what I could find out with the help
of other maven users here on the list.

Amit

On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote:
> Hello
>
> I have a question re dependency resolution of the maven-war-plugin.
> If I run 'mvn install' a war is built including the library xbeans.jar
> (xmlbeans:xbean is a transitive dependency of a plugin). Why is this
> dependency included though not declared?
>
> A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns
> with no result. It seems to me that maven-war-plugin includes also
> transitive plugin dependencies.
>
> Thanks for your help, Felix
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

RE: Maven2 and artifact versions

[Simon Kitching]

 "Jörg Schaible" <[EMAIL PROTECTED]> schrieb:
> Simon Kitching wrote:
> 
> [snip]
> 
> > Personally, I prefer the second because it is clear to all
> > readers that yes a version *is* being specified for this
> > dependency. With the dependencyManagement approach, it isn't
> > clear unless you check the parent pom. However I appear to be
> > in the minority, with many people preferring dependencyManagement.
> 
> Because the dependencyManagement also define the version of the transitive 
> deps (at least it should since M206).

Good point. Using the $foo approach only works for direct 
dependencies; it cannot be used to influence the selected version for a 
transitive dependency.

However if you want dependencyManagement to apply to transient deps, you would 
really need to use [x.y] or [x.y,z.a] version numbers, right?

If a pom has a dependencyManagement declaration of 
  1.0
but some required lib declares a dependency on the same artifact using
   [1.2,1.4]
then what will happen?

I presume that version 1.2 will be used, ie the dependencyManagement 
declaration is ignored. If that is true, then it cannot actually be relied on 
unless dependencyManagement uses explicitly locked versions (or ranges).

Regards,
Simon

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

RE: Checkstyle Problem

[nicklist]

What goals are you running from continuum?

You could attach the checkstyle:checkstyle goal to another phase:



org.apache.maven.plugins
maven-checkstyle-plugin



run

verify






Hth,

Nick Stolwijk

-Original Message-
From: Mitesh51 [mailto:[EMAIL PROTECTED]
Sent: Thu 1/31/2008 11:40 AM
To: [EMAIL PROTECTED]
Subject: RE: Checkstyle Problem
 

What i want to do is generate a checkstyle report.

I can do thais via mvn checkstyle:checkstyle from command prompt but i am
not able to generate that report when i use the continumm to run the Maven
project.

If u have yahoo id then can u give me?

Please I need the solution very urgently. 


nicklist wrote:
> 
> What goals or phase are you running from Continuum? The reporting section
> is only used when generating a site (thus, running mvn site) and not when
> running an install or deploy.
> 
> Hth,
> 
> Nick Stolwijk
> 
> ps. I don't think you need the checkstyle artifact as dependency. This way
> it will be included in your project.
> 
> 
> -Original Message-
> From: Mitesh51 [mailto:[EMAIL PROTECTED]
> Sent: Thu 1/31/2008 11:07 AM
> To: [EMAIL PROTECTED]
> Subject: Checkstyle Problem
>  
> 
> I want to use checkstyle plugin and use it in continuum.
> 
> My pom.xml looks like .
> 
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>   4.0.0
>   com.mycompany.app
>   my-app
>   jar
>   1.0-SNAPSHOT
>   my-app
>   http://maven.apache.org
> 
>   
> 
> scm:svn:svn://shikhas:[EMAIL 
> PROTECTED]/iLabsDevRepo/Source/trunk/iTraining/trunk/maven/my-app/
>   
> 
> 
>   
>
>   checkstyle
>   checkstyle
>   4.1
> jar
>   package
> true
> 
> 
>   
> 
>
>  
>  
>
> org.apache.maven.plugins 
>
> maven-checkstyle-plugin 
>  
> D:\ILabs
> Task\Maven\checkstyle-4.4\sun_checks.xml 
>  
>  
>  
>  
> 
> 
> 
> It is downloading the jars necessary for the checkstyle but it is not
> generating the checkstyle documents.
> 
> Is there anything missing in pom.xml?
> 
> After running the build script in continuum, It does not generate the
> checkstyle reports in the Output directory with the use of continuum.
> 
> Any Suggestions??
> -- 
> View this message in context:
> http://www.nabble.com/Checkstyle-Problem-tp15201303p15201303.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Checkstyle-Problem-tp15201303p15201976.html
Sent from the Continuum - Users mailing list archive at Nabble.com.

Re: Dependency resolution of maven-war-plugin

[amit kumar]

Yes Felix maven-war-plugin does include the transitive dependencies.
For a transitive dependency of a plugin, the way(workaround) I found
and using is to declare that dependency explicitly in your pom.xml and
declare it to be available at only compile time (  tag).

For the transitive dependencies of the rest of the dependencies I am
using  tag with in the dependency tag. That probably be not
the sanest way of it, but this was what I could find out with the help
of other maven users here on the list.

Amit

On Jan 31, 2008 4:20 PM, Felix Röthenbacher <[EMAIL PROTECTED]> wrote:
> Hello
>
> I have a question re dependency resolution of the maven-war-plugin.
> If I run 'mvn install' a war is built including the library xbeans.jar
> (xmlbeans:xbean is a transitive dependency of a plugin). Why is this
> dependency included though not declared?
>
> A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns
> with no result. It seems to me that maven-war-plugin includes also
> transitive plugin dependencies.
>
> Thanks for your help, Felix
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

RE: Checkstyle Problem

[MATHUS Baptiste]

Hi,

If you need something urgently as you say, better would be to try to answer 
questions asked by those who try to help you :-). 

*What goal did you configure inside Continuum for your project ?*

To generate the reports, you have to use "mvn site" at least. If not, the site, 
and so the integrated reports won't be generated.

Cheers.

-Message d'origine-
De : Mitesh51 [mailto:[EMAIL PROTECTED] 
Envoyé : jeudi 31 janvier 2008 11:40
À : [EMAIL PROTECTED]
Objet : RE: Checkstyle Problem


What i want to do is generate a checkstyle report.

I can do thais via mvn checkstyle:checkstyle from command prompt but i am not 
able to generate that report when i use the continumm to run the Maven project.

If u have yahoo id then can u give me?

Please I need the solution very urgently. 


nicklist wrote:
> 
> What goals or phase are you running from Continuum? The reporting 
> section is only used when generating a site (thus, running mvn site) 
> and not when running an install or deploy.
> 
> Hth,
> 
> Nick Stolwijk
> 
> ps. I don't think you need the checkstyle artifact as dependency. This 
> way it will be included in your project.
> 
> 
> -Original Message-
> From: Mitesh51 [mailto:[EMAIL PROTECTED]
> Sent: Thu 1/31/2008 11:07 AM
> To: [EMAIL PROTECTED]
> Subject: Checkstyle Problem
>  
> 
> I want to use checkstyle plugin and use it in continuum.
> 
> My pom.xml looks like .
> 
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>   4.0.0
>   com.mycompany.app
>   my-app
>   jar
>   1.0-SNAPSHOT
>   my-app
>   http://maven.apache.org
> 
>   
> 
> scm:svn:svn://shikhas:[EMAIL 
> PROTECTED]/iLabsDevRepo/Source/trunk/iTraining/trunk/maven/my-app/
>   
> 
> 
>   
>
>   checkstyle
>   checkstyle
>   4.1
> jar
>   package
> true
> 
> 
>   
> 
>
>  
> 
>
> org.apache.maven.plugins
>
> maven-checkstyle-plugin 
>  
> D:\ILabs 
> Task\Maven\checkstyle-4.4\sun_checks.xml
>  
>  
>  
> 
> 
> 
> 
> It is downloading the jars necessary for the checkstyle but it is not 
> generating the checkstyle documents.
> 
> Is there anything missing in pom.xml?
> 
> After running the build script in continuum, It does not generate the 
> checkstyle reports in the Output directory with the use of continuum.
> 
> Any Suggestions??
> --
> View this message in context:
> http://www.nabble.com/Checkstyle-Problem-tp15201303p15201303.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
> 
> 
> 
> 

--
View this message in context: 
http://www.nabble.com/Checkstyle-Problem-tp15201303p15201976.html
Sent from the Continuum - Users mailing list archive at Nabble.com.

Dependency resolution of maven-war-plugin

[Felix Röthenbacher]

Hello

I have a question re dependency resolution of the maven-war-plugin.
If I run 'mvn install' a war is built including the library xbeans.jar
(xmlbeans:xbean is a transitive dependency of a plugin). Why is this
dependency included though not declared?

A check with 'mvn dependency:tree -Dincludes=xmlbeans:xbean' returns
with no result. It seems to me that maven-war-plugin includes also
transitive plugin dependencies.

Thanks for your help, Felix


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

Re: maven renaming jar files

[amit kumar]

I have overcome the problem. And guess know the reason for that,
actually at the time of creating the LAN maven repository, I have
installed common components under org.apache.commons groupId (
assuming the convention of groupId as package name ). So now when I
was including commons-logging as dependency in my pom.xml,
what I added to pom looked like

org.apache.commons
commons-logging
1.1

But there was another dependency in my pom.xml which as
commons-logging as transitive dependency with same version, so what
was happening(probably) was that maven instead of overriding the jar
file was renaming it, may be because the jars were differently
identified as groupId+artifactId+version.
Still a little confused about my own explanation of the happenings :)

Amit

On Jan 30, 2008 9:51 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Looks weird.
> Do you use a released version ? or the current snapshot ?
>
> Could you load an issue in jira with a simple project which reproduce this ?
>
> --
> Olivier
>
> 2008/1/30, amit kumar <[EMAIL PROTECTED]>:
>
> > Hi,.
> > When I am packaging a WAR project, I am seeing the following thing 
> > happening...
> >
> > [DEBUG] Processing: commons-logging-1.1.jar
> > [DEBUG] Duplicate found: commons-logging-1.1.jar
> > [DEBUG] Renamed to: commons-logging-commons-logging-1.1.jar
> >
> > Any idea why this happens and how to avoid this?
> > I am mentioning commons-logging-1.1 as my dependency in the pom.xml,
> > and have suppressed the other versions of commons logging which were
> > getting packaged as transitive dependencies of project dependencies
> > using  tag in dependency taf. Same is happening with
> > commons-digester and other dependencies.
> >
> >
> > Regards,
> > Amit
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

RE: Checkstyle Problem

[Mitesh51]

What i want to do is generate a checkstyle report.

I can do thais via mvn checkstyle:checkstyle from command prompt but i am
not able to generate that report when i use the continumm to run the Maven
project.

If u have yahoo id then can u give me?

Please I need the solution very urgently. 


nicklist wrote:
> 
> What goals or phase are you running from Continuum? The reporting section
> is only used when generating a site (thus, running mvn site) and not when
> running an install or deploy.
> 
> Hth,
> 
> Nick Stolwijk
> 
> ps. I don't think you need the checkstyle artifact as dependency. This way
> it will be included in your project.
> 
> 
> -Original Message-
> From: Mitesh51 [mailto:[EMAIL PROTECTED]
> Sent: Thu 1/31/2008 11:07 AM
> To: [EMAIL PROTECTED]
> Subject: Checkstyle Problem
>  
> 
> I want to use checkstyle plugin and use it in continuum.
> 
> My pom.xml looks like .
> 
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>   4.0.0
>   com.mycompany.app
>   my-app
>   jar
>   1.0-SNAPSHOT
>   my-app
>   http://maven.apache.org
> 
>   
> 
> scm:svn:svn://shikhas:[EMAIL 
> PROTECTED]/iLabsDevRepo/Source/trunk/iTraining/trunk/maven/my-app/
>   
> 
> 
>   
>
>   checkstyle
>   checkstyle
>   4.1
> jar
>   package
> true
> 
> 
>   
> 
>
>  
>  
>
> org.apache.maven.plugins 
>
> maven-checkstyle-plugin 
>  
> D:\ILabs
> Task\Maven\checkstyle-4.4\sun_checks.xml 
>  
>  
>  
>  
> 
> 
> 
> It is downloading the jars necessary for the checkstyle but it is not
> generating the checkstyle documents.
> 
> Is there anything missing in pom.xml?
> 
> After running the build script in continuum, It does not generate the
> checkstyle reports in the Output directory with the use of continuum.
> 
> Any Suggestions??
> -- 
> View this message in context:
> http://www.nabble.com/Checkstyle-Problem-tp15201303p15201303.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Checkstyle-Problem-tp15201303p15201976.html
Sent from the Continuum - Users mailing list archive at Nabble.com.

RE: Maven2 and artifact versions

[Jörg Schaible]

Simon Kitching wrote:

[snip]

> Personally, I prefer the second because it is clear to all
> readers that yes a version *is* being specified for this
> dependency. With the dependencyManagement approach, it isn't
> clear unless you check the parent pom. However I appear to be
> in the minority, with many people preferring dependencyManagement.

Because the dependencyManagement also define the version of the transitive deps 
(at least it should since M206).

- Jörg

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

[ANN] Maven2 Dependency Analyzer 1.1-rc0 released

[Dror Bereznitsky]

We are pleased to announce the release of Dependency Analyzer version
1.1-rc0

http://www.jfrog.org/sites/dep-analyzer/latest/

Release notes:
--
Bug

   - [MDV-51 ] - FATAL exception
   when starting dependency analyzer
   - [MDV-54 ] - Cannot start
   dependency analyzer in path with blank spaces
   - [MDV-55 ] - Viewer ignores
   dependencies, when marked as optional
   - [MDV-61 ] - Optional
   dependency gets displayed, when dependent vertex has a mandatory edge, too.

Documentation

   - [MDV-49 ] - Required
   propeties

Improvement

   - [MDV-47 ] - Don't show
   excluded dependencies by default
   - [MDV-48 ] - Better error
   messages for startup
   - [MDV-52 ] - A refresh
   option
   - [MDV-53 ] - Make it
   possible to copy dependency test to clipboard

New Feature

   - [MDV-32 ] - Analyzing a
   Maven project
   - [MDV-42 ] - Missing
   progress bar
   - [MDV-46 ] - A packaging
   information to vertex tooltip

Sub-task

   - [MDV-44 ] - Add modules
   support

Enjoy,
Dror Bereznitsky
The Jfrog Team

Re: Clearcase Snapshot View Synchronisation

[Kalle Korhonen]

Absolutely. We have an additional "stable label" system in use - this
dynamic view only picks up what's being promoted as stable, so accidental
changes are not a practical issue for us (but without it, certainly would
be).

Kalle


On 1/31/08, Jan Fredrik Wedén <[EMAIL PROTECTED]> wrote:
>
> On Jan 25, 2008 6:25 PM, Kalle Korhonen <[EMAIL PROTECTED]>
> wrote:
> > Same here, dynamic views with Continuum as a build server. There were
> some
> > quirks making it play nice with ClearCase, but generally works ok (and
> yes,
> > svn is way superior).
> >
> > Kalle
> >
>
> If using dynamic views, don't you run into the potential risk of the
> view contents being updated in the middle of a build?
>
> As for the original question: we solved a similar issue using
> CruiseControl's composite builder and then running some ClearCase
> operations using an Ant script before we kicked off the Maven build.
>
> --
> - Jan Fredrik Wedén
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Maven plugins that can check for hardcoded (un-externalized) strings at build time? (i18n)

[Rémy Sanlaville]

Hi,

I don't think so but it will be a useful plugin.

Rémy

Re: Clearcase Snapshot View Synchronisation

[Jan Fredrik Wedén]

On Jan 25, 2008 6:25 PM, Kalle Korhonen <[EMAIL PROTECTED]> wrote:
> Same here, dynamic views with Continuum as a build server. There were some
> quirks making it play nice with ClearCase, but generally works ok (and yes,
> svn is way superior).
>
> Kalle
>

If using dynamic views, don't you run into the potential risk of the
view contents being updated in the middle of a build?

As for the original question: we solved a similar issue using
CruiseControl's composite builder and then running some ClearCase
operations using an Ant script before we kicked off the Maven build.

-- 
- Jan Fredrik Wedén

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

Re: Maven2 and artifact versions

[amidrunk]

Thanks, both of you!

Regards,
Nille


Simon Kitching-4 wrote:
> 
>  Guillaume Lederrey <[EMAIL PROTECTED]> schrieb:
>> On 31/01/2008, amidrunk <[EMAIL PROTECTED]> wrote:
>> > Is there any good way to manage versions of dependencies in maven? In
>> maven1
>> > it was possible to define the version in a properties file in a root
>> > project. Is there something similiar in maven2? Right now we define the
>> > versions in settings.xml, but that is not a feasible long-term
>> solution.
>> 
>> 
>> Have a look at dependencyManagement :
>> http://maven.apache.org/pom#Dependency_Management
> 
> Yep, using dependncyManagement in a parent pom will allow you to then have
>> > 
>> >com.mycompany
>> >myArtifact
>> > 
> 
> The alternative is to do this in a parent pom:
> 
>   1.1
> 
> 
> That will allow you to have:
>> > 
>> >com.mycompany
>> >myArtifact
>> >${com.mycompany.version}
>> > 
> 
> Personally, I prefer the second because it is clear to all readers that
> yes a version *is* being specified for this dependency. With the
> dependencyManagement approach, it isn't clear unless you check the parent
> pom. However I appear to be in the minority, with many people preferring
> dependencyManagement.
> 
> Regards, Simon
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Maven2-and-artifact-versions-tp15199790s177p15200597.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Maven2 and artifact versions

[Simon Kitching]

 Guillaume Lederrey <[EMAIL PROTECTED]> schrieb:
> On 31/01/2008, amidrunk <[EMAIL PROTECTED]> wrote:
> > Is there any good way to manage versions of dependencies in maven? In maven1
> > it was possible to define the version in a properties file in a root
> > project. Is there something similiar in maven2? Right now we define the
> > versions in settings.xml, but that is not a feasible long-term solution.
> 
> 
> Have a look at dependencyManagement :
> http://maven.apache.org/pom#Dependency_Management

Yep, using dependncyManagement in a parent pom will allow you to then have
> > 
> >com.mycompany
> >myArtifact
> > 

The alternative is to do this in a parent pom:

  1.1


That will allow you to have:
> > 
> >com.mycompany
> >myArtifact
> >${com.mycompany.version}
> > 

Personally, I prefer the second because it is clear to all readers that yes a 
version *is* being specified for this dependency. With the dependencyManagement 
approach, it isn't clear unless you check the parent pom. However I appear to 
be in the minority, with many people preferring dependencyManagement.

Regards, Simon

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

Re: Maven2 and artifact versions

[Guillaume Lederrey]

On 31/01/2008, amidrunk <[EMAIL PROTECTED]> wrote:
> Is there any good way to manage versions of dependencies in maven? In maven1
> it was possible to define the version in a properties file in a root
> project. Is there something similiar in maven2? Right now we define the
> versions in settings.xml, but that is not a feasible long-term solution.


Have a look at dependencyManagement :
http://maven.apache.org/pom#Dependency_Management


> We would either like to leave the version in a dependency and have e.g.
>
> 
>com.mycompany
>myArtifact
> 
>
> Or we would like to have:
>
> 
>com.mycompany
>myArtifact
>${com.mycompany.version}
> 
>
> Thanks in advance,
> Nille
> --
> View this message in context: 
> http://www.nabble.com/Maven2-and-artifact-versions-tp15199790s177p15199790.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Jabber : [EMAIL PROTECTED]
Skype : Guillaume.Lederrey
Projects :
* http://rwanda.wordpress.com/

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

Maven2 and artifact versions

[amidrunk]

Hi,

Is there any good way to manage versions of dependencies in maven? In maven1
it was possible to define the version in a properties file in a root
project. Is there something similiar in maven2? Right now we define the
versions in settings.xml, but that is not a feasible long-term solution.

We would either like to leave the version in a dependency and have e.g.


   com.mycompany
   myArtifact


Or we would like to have:


   com.mycompany
   myArtifact
   ${com.mycompany.version}


Thanks in advance,
Nille
-- 
View this message in context: 
http://www.nabble.com/Maven2-and-artifact-versions-tp15199790s177p15199790.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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