Custom Archetypes: Creating empty directories

2009-11-19 Thread Richard Hauswald
Hello list,
I'm trying to create a custom archetype. All is working fine except
that I can't create empty directories. Is this impossible or do miss
something?
Thanks,
Richard
-- 
Richard Hauswald
Blog: http://tnfstacc.blogspot.com/
LinkedIn: http://www.linkedin.com/in/richardhauswald
Xing: http://www.xing.com/profile/Richard_Hauswald

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



Re: How best to deploy ( different config ) to different machines

2009-11-19 Thread Anders Hammar
This is a generic Java question. It doesn't matter if you use Maven or, for
instance, Ant to build your Java EE app.

Read the properties file from class path. Then make sure that the properties
file is on the class path in the container (but outside of the ear), in each
environment. In JBoss for instance, one way is to put the properties file in
the conf folder.
However, you could also read config values from JNDI. Then make sure that
the JNDI tree is populated correctly for each environment.

/Anders

On Fri, Nov 20, 2009 at 01:32, Sony Antony  wrote:

> I was thinking of exactly teh same when I wrote it ( the name of the
> particular config file to be chosen is stored in JNDI. Using the
> application
> event listener, teh particular file is preread when app comes online )
>
> But I wanted to ask if this is really how most well maintained projects do
> it ?
>
> Does maven have any tricks/standard way to deploy teh config file ?
> --sony
>
>
>
>
> On Thu, Nov 19, 2009 at 7:28 PM, Jesse Farinacci  wrote:
>
> > Sounds like a job for JNDI.
> >
> > On Thu, Nov 19, 2009 at 7:23 PM, Sony Antony 
> > wrote:
> > > Reading the following thread brings forth this question ( Actually
> there
> > was
> > > a thread on this few weeks back. But it wasnt very detailed ) :
> > >
> > > We have this configuration file that contains machine/server specific
> > > information.
> > > Assuming my application is an ear, how do I do a build so that I dont
> > have
> > > to do a build specific for each target hosts.
> > > 1. Should I bundle up the configuration file inside the ear file ?
> > > 2. Should I bundle up all configuration files for all possible servers
> > and
> > > at deployment time set some kind of variable ( through teh app server
> > admin
> > > console ), which resolves to a specific config file ?
> > >
> > > In general what is teh best practice for this
> > > --sony
> > >
> >
> > -Jesse
> >
> > --
> > There are 10 types of people in this world, those
> > that can read binary and those that can not.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>


Re: Isn't listing a dependency supposed to download that JAR file into your WEB-INF/lib folder?

2009-11-19 Thread Anders Hammar
They should. Two reasons why they aren't that I can think of right now are:
1. Their scope is provided
2. The war plugin is configured to exclude them (param 'packagingExcludes'
or 'packagingIncludes').

Run help:effective-pom to get the effective pom to see the complete picture.
mvn install -X would also give you (a lot) more info on what is going on.

/Anders

On Thu, Nov 19, 2009 at 23:04, laredotornado wrote:

>
> I'm using Maven 2.2 on Mac 10.5.6 with JBoss 5.1.  I have these two
> dependencies in my pom.xml (I'm building a WAR file) ...
>
>
>  com.myco.jsf
>  com-myco-jsf
>  1.11
>
>
>  myco.util.jsf
>  myco-util-jsf
>  1.3
>
>
> I can compile and build my project fine using
>
> mvn clean install jboss:redeploy
>
> However when I open up my WAR file, the two JAR files listed above are not
> there.  Why not?  Anyone know how to include them?
>
> Thanks,  - Dave
> --
> View this message in context:
> http://old.nabble.com/Isn%27t-listing-a-dependency-supposed-to-download-that-JAR-file-into-your-WEB-INF-lib-folder--tp26421497p26421497.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Ellecer Valencia
No, not my team. I think a more sensible fix is to just put the
weblogic jars in Artifactory, but it's in a pom that I don't have much
control over.

Maybe 2.2.2 will fix it. =)

On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall  wrote:
> http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that :).
>
> On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia  wrote:
>
>> Hi Brett,
>>
>> Thanks for the suggestion. I may have found the issue. Would it be this:
>>
>>
>> Validation Errors:
>> [DEBUG] For dependency Dependency {groupId=weblogic,
>> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
>> must specify an absolute path systemPath.
>> [DEBUG] For managed dependency Dependency {groupId=weblogic,
>> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
>> must specify an absolute path systemPath.
>> [DEBUG]
>>
>> [DEBUG]   mypackage:myartifact:jar:1.0.2:compile (selected for compile)
>> [DEBUG] Skipping disabled repository central
>> [DEBUG] myartifact: using locally installed snapshot
>> [WARNING] POM for 'mypackage:myartifact:pom:1.0.2-SNAPSHOT:test' is
>> invalid.
>>
>> Its dependencies (if any) will NOT be available to the current build.
>> [DEBUG] Reason: Failed to validate POM for project
>> mypackage:myartifact at Artifact
>> [mypackage:myartifact:pom:1.0.2-SNAPSHOT:test]
>> [DEBUG]
>> Validation Errors:
>> [DEBUG] For dependency Dependency {groupId=weblogic,
>> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
>> must specify an absolute path systemPath.
>> [DEBUG] For dependency Dependency {groupId=weblogic,
>> artifactId=webservices, version=10.0, type=jar}: system-scoped
>> dependency must specify an absolute path systemPath.
>> [DEBUG] For managed dependency Dependency {groupId=weblogic,
>> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
>> must specify an absolute path systemPath.
>> [DEBUG] For managed dependency Dependency {groupId=weblogic,
>> artifactId=webservices, version=10.0, type=jar}: system-scoped
>> dependency must specify an absolute path systemPath.
>> [DEBUG]
>>
>>
>> Now in this project, we are inheriting from a parent POM (standardised
>> for our department) with entries like this:
>> (WL_HOME is Weblogic install directory)
>>
>>
>>      
>>        com.sun
>>        tools
>>        1.5.0.11
>>        system
>>        ${java.home}/../lib/tools.jar
>>      
>>      
>>        com.sun
>>        rt
>>        1.5.0.11
>>        system
>>        ${java.home}/lib/rt.jar
>>      
>>      
>>        weblogic
>>        weblogic
>>        10.0
>>        system
>>        ${env.WL_HOME}/server/lib/weblogic.jar
>>      
>>      
>>        weblogic
>>        webservices
>>        10.0
>>        system
>>        ${env.WL_HOME}/server/lib/webservices.jar
>>      
>>
>>
>> Now it only fails on the Weblogic related entries. With the Java
>> system dependencies it seems to do fine.
>>
>> Has the handling of this changed from 2.0.* to 2.2.*?
>>
>> If so, what should we replace it with?
>>
>> And will these settings also work for  people still using maven 2.0.10?
>>
>>
>> Ellecer
>>
>>
>>
>> On Fri, Nov 20, 2009 at 1:01 PM, Brett Randall 
>> wrote:
>> > Hi Ellecer
>> >
>> > What is the output of mvn -e -X ...
>> >
>> > Brett
>> >
>> > On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia > >wrote:
>> >
>> >> Hi,
>> >>
>> >> How come when I try a build using Maven 2.2.1 I get multiple messages
>> like
>> >> this:
>> >>
>> >> "[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is
>> >> invalid.
>> >>
>> >> Its dependencies (if any) will NOT be available to the current build."
>> >>
>> >> These errors weren't displaying when I was using Maven 2.0.10
>> >>
>> >> I'm trying to use the newer version of Maven but I can't proceed with
>> >> these error messages.
>> >>
>> >> How can I find out what are the actual errors it's referring to? I
>> >> didn't come across any mention of relevant POM format changes going
>> >> from Maven 2.0.* to 2.1.* or 2.2.* - if anyone has any info on this it
>> >> would be a great help!  Is there a way to validate the pom and get
>> >> format error details  from Maven?
>> >>
>> >>
>> >> thanks,
>> >>
>> >> Ellecer
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: users-h...@maven.apache.org
>> >>
>> >>
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>

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



Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Brett Randall
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that :).

On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia  wrote:

> Hi Brett,
>
> Thanks for the suggestion. I may have found the issue. Would it be this:
>
>
> Validation Errors:
> [DEBUG] For dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
> [DEBUG]
>
> [DEBUG]   mypackage:myartifact:jar:1.0.2:compile (selected for compile)
> [DEBUG] Skipping disabled repository central
> [DEBUG] myartifact: using locally installed snapshot
> [WARNING] POM for 'mypackage:myartifact:pom:1.0.2-SNAPSHOT:test' is
> invalid.
>
> Its dependencies (if any) will NOT be available to the current build.
> [DEBUG] Reason: Failed to validate POM for project
> mypackage:myartifact at Artifact
> [mypackage:myartifact:pom:1.0.2-SNAPSHOT:test]
> [DEBUG]
> Validation Errors:
> [DEBUG] For dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
> [DEBUG] For dependency Dependency {groupId=weblogic,
> artifactId=webservices, version=10.0, type=jar}: system-scoped
> dependency must specify an absolute path systemPath.
> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> artifactId=webservices, version=10.0, type=jar}: system-scoped
> dependency must specify an absolute path systemPath.
> [DEBUG]
>
>
> Now in this project, we are inheriting from a parent POM (standardised
> for our department) with entries like this:
> (WL_HOME is Weblogic install directory)
>
>
>  
>com.sun
>tools
>1.5.0.11
>system
>${java.home}/../lib/tools.jar
>  
>  
>com.sun
>rt
>1.5.0.11
>system
>${java.home}/lib/rt.jar
>  
>  
>weblogic
>weblogic
>10.0
>system
>${env.WL_HOME}/server/lib/weblogic.jar
>  
>  
>weblogic
>webservices
>10.0
>system
>${env.WL_HOME}/server/lib/webservices.jar
>  
>
>
> Now it only fails on the Weblogic related entries. With the Java
> system dependencies it seems to do fine.
>
> Has the handling of this changed from 2.0.* to 2.2.*?
>
> If so, what should we replace it with?
>
> And will these settings also work for  people still using maven 2.0.10?
>
>
> Ellecer
>
>
>
> On Fri, Nov 20, 2009 at 1:01 PM, Brett Randall 
> wrote:
> > Hi Ellecer
> >
> > What is the output of mvn -e -X ...
> >
> > Brett
> >
> > On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia  >wrote:
> >
> >> Hi,
> >>
> >> How come when I try a build using Maven 2.2.1 I get multiple messages
> like
> >> this:
> >>
> >> "[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is
> >> invalid.
> >>
> >> Its dependencies (if any) will NOT be available to the current build."
> >>
> >> These errors weren't displaying when I was using Maven 2.0.10
> >>
> >> I'm trying to use the newer version of Maven but I can't proceed with
> >> these error messages.
> >>
> >> How can I find out what are the actual errors it's referring to? I
> >> didn't come across any mention of relevant POM format changes going
> >> from Maven 2.0.* to 2.1.* or 2.2.* - if anyone has any info on this it
> >> would be a great help!  Is there a way to validate the pom and get
> >> format error details  from Maven?
> >>
> >>
> >> thanks,
> >>
> >> Ellecer
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Ellecer Valencia
Hi Brett,

Thanks for the suggestion. I may have found the issue. Would it be this:


Validation Errors:
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
[DEBUG]

[DEBUG]   mypackage:myartifact:jar:1.0.2:compile (selected for compile)
[DEBUG] Skipping disabled repository central
[DEBUG] myartifact: using locally installed snapshot
[WARNING] POM for 'mypackage:myartifact:pom:1.0.2-SNAPSHOT:test' is invalid.

Its dependencies (if any) will NOT be available to the current build.
[DEBUG] Reason: Failed to validate POM for project
mypackage:myartifact at Artifact
[mypackage:myartifact:pom:1.0.2-SNAPSHOT:test]
[DEBUG]
Validation Errors:
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=webservices, version=10.0, type=jar}: system-scoped
dependency must specify an absolute path systemPath.
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=webservices, version=10.0, type=jar}: system-scoped
dependency must specify an absolute path systemPath.
[DEBUG]


Now in this project, we are inheriting from a parent POM (standardised
for our department) with entries like this:
(WL_HOME is Weblogic install directory)


  
com.sun
tools
1.5.0.11
system
${java.home}/../lib/tools.jar
  
  
com.sun
rt
1.5.0.11
system
${java.home}/lib/rt.jar
  
  
weblogic
weblogic
10.0
system
${env.WL_HOME}/server/lib/weblogic.jar
  
  
weblogic
webservices
10.0
system
${env.WL_HOME}/server/lib/webservices.jar
  


Now it only fails on the Weblogic related entries. With the Java
system dependencies it seems to do fine.

Has the handling of this changed from 2.0.* to 2.2.*?

If so, what should we replace it with?

And will these settings also work for  people still using maven 2.0.10?


Ellecer



On Fri, Nov 20, 2009 at 1:01 PM, Brett Randall  wrote:
> Hi Ellecer
>
> What is the output of mvn -e -X ...
>
> Brett
>
> On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia wrote:
>
>> Hi,
>>
>> How come when I try a build using Maven 2.2.1 I get multiple messages like
>> this:
>>
>> "[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is
>> invalid.
>>
>> Its dependencies (if any) will NOT be available to the current build."
>>
>> These errors weren't displaying when I was using Maven 2.0.10
>>
>> I'm trying to use the newer version of Maven but I can't proceed with
>> these error messages.
>>
>> How can I find out what are the actual errors it's referring to? I
>> didn't come across any mention of relevant POM format changes going
>> from Maven 2.0.* to 2.1.* or 2.2.* - if anyone has any info on this it
>> would be a great help!  Is there a way to validate the pom and get
>> format error details  from Maven?
>>
>>
>> thanks,
>>
>> Ellecer
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>

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



Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Brett Randall
Hi Ellecer

What is the output of mvn -e -X ...

Brett

On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia wrote:

> Hi,
>
> How come when I try a build using Maven 2.2.1 I get multiple messages like
> this:
>
> "[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is
> invalid.
>
> Its dependencies (if any) will NOT be available to the current build."
>
> These errors weren't displaying when I was using Maven 2.0.10
>
> I'm trying to use the newer version of Maven but I can't proceed with
> these error messages.
>
> How can I find out what are the actual errors it's referring to? I
> didn't come across any mention of relevant POM format changes going
> from Maven 2.0.* to 2.1.* or 2.2.* - if anyone has any info on this it
> would be a great help!  Is there a way to validate the pom and get
> format error details  from Maven?
>
>
> thanks,
>
> Ellecer
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


"[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

2009-11-19 Thread Ellecer Valencia
Hi,

How come when I try a build using Maven 2.2.1 I get multiple messages like this:

"[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is invalid.

Its dependencies (if any) will NOT be available to the current build."

These errors weren't displaying when I was using Maven 2.0.10

I'm trying to use the newer version of Maven but I can't proceed with
these error messages.

How can I find out what are the actual errors it's referring to? I
didn't come across any mention of relevant POM format changes going
from Maven 2.0.* to 2.1.* or 2.2.* - if anyone has any info on this it
would be a great help!  Is there a way to validate the pom and get
format error details  from Maven?


thanks,

Ellecer

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



Re: How best to deploy ( different config ) to different machines

2009-11-19 Thread Sony Antony
I was thinking of exactly teh same when I wrote it ( the name of the
particular config file to be chosen is stored in JNDI. Using the application
event listener, teh particular file is preread when app comes online )

But I wanted to ask if this is really how most well maintained projects do
it ?

Does maven have any tricks/standard way to deploy teh config file ?
--sony




On Thu, Nov 19, 2009 at 7:28 PM, Jesse Farinacci  wrote:

> Sounds like a job for JNDI.
>
> On Thu, Nov 19, 2009 at 7:23 PM, Sony Antony 
> wrote:
> > Reading the following thread brings forth this question ( Actually there
> was
> > a thread on this few weeks back. But it wasnt very detailed ) :
> >
> > We have this configuration file that contains machine/server specific
> > information.
> > Assuming my application is an ear, how do I do a build so that I dont
> have
> > to do a build specific for each target hosts.
> > 1. Should I bundle up the configuration file inside the ear file ?
> > 2. Should I bundle up all configuration files for all possible servers
> and
> > at deployment time set some kind of variable ( through teh app server
> admin
> > console ), which resolves to a specific config file ?
> >
> > In general what is teh best practice for this
> > --sony
> >
>
> -Jesse
>
> --
> There are 10 types of people in this world, those
> that can read binary and those that can not.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


Re: How best to deploy ( different config ) to different machines

2009-11-19 Thread Jesse Farinacci
Sounds like a job for JNDI.

On Thu, Nov 19, 2009 at 7:23 PM, Sony Antony  wrote:
> Reading the following thread brings forth this question ( Actually there was
> a thread on this few weeks back. But it wasnt very detailed ) :
>
> We have this configuration file that contains machine/server specific
> information.
> Assuming my application is an ear, how do I do a build so that I dont have
> to do a build specific for each target hosts.
> 1. Should I bundle up the configuration file inside the ear file ?
> 2. Should I bundle up all configuration files for all possible servers and
> at deployment time set some kind of variable ( through teh app server admin
> console ), which resolves to a specific config file ?
>
> In general what is teh best practice for this
> --sony
>

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

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



How best to deploy ( different config ) to different machines

2009-11-19 Thread Sony Antony
Reading the following thread brings forth this question ( Actually there was
a thread on this few weeks back. But it wasnt very detailed ) :

We have this configuration file that contains machine/server specific
information.
Assuming my application is an ear, how do I do a build so that I dont have
to do a build specific for each target hosts.
1. Should I bundle up the configuration file inside the ear file ?
2. Should I bundle up all configuration files for all possible servers and
at deployment time set some kind of variable ( through teh app server admin
console ), which resolves to a specific config file ?

In general what is teh best practice for this


--sony




On Thu, Nov 19, 2009 at 6:24 PM, Wagner Santos wrote:

> Thanks! It's work (with some modifications).
>
> --
> Wagner Santos
> MSN/Gtalk: wagner.gsan...@gmail.com
> Site: http://www.geracaoelias.blog.br
> meadiciona:http://meadiciona.com/wagnergsantos/
>
>
> On Thu, Nov 19, 2009 at 1:00 AM, Wayne Fay  wrote:
>
> > > I have a webapp and two servers and a localhost with diferents
> databases
> > > configs and I'm trying to do this:
> >
> > In general, you should use profiles for this kind of thing:
> >
> >
> http://maven.apache.org/guides/mini/guide-building-for-different-environments.html
> >
> > Wayne
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>


Re: Build multiples war with multiples contexts.

2009-11-19 Thread Wagner Santos
Thanks! It's work (with some modifications).

--
Wagner Santos
MSN/Gtalk: wagner.gsan...@gmail.com
Site: http://www.geracaoelias.blog.br
meadiciona:http://meadiciona.com/wagnergsantos/


On Thu, Nov 19, 2009 at 1:00 AM, Wayne Fay  wrote:

> > I have a webapp and two servers and a localhost with diferents databases
> > configs and I'm trying to do this:
>
> In general, you should use profiles for this kind of thing:
>
> http://maven.apache.org/guides/mini/guide-building-for-different-environments.html
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


Re: findbugs-plugin: Premature end of file.

2009-11-19 Thread duality72

I'm having the same problem today. Looks like the findbugs plugin has been
updated to version 2.2 and is causing the problem. Reverting to version
2.0.1 has removed the problem.
-- 
View this message in context: 
http://old.nabble.com/findbugs-plugin%3A-Premature-end-of-file.-tp26421353p26421509.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Isn't listing a dependency supposed to download that JAR file into your WEB-INF/lib folder?

2009-11-19 Thread laredotornado

I'm using Maven 2.2 on Mac 10.5.6 with JBoss 5.1.  I have these two
dependencies in my pom.xml (I'm building a WAR file) ...


  com.myco.jsf
  com-myco-jsf
  1.11


  myco.util.jsf
  myco-util-jsf
  1.3


I can compile and build my project fine using 

mvn clean install jboss:redeploy

However when I open up my WAR file, the two JAR files listed above are not
there.  Why not?  Anyone know how to include them?

Thanks,  - Dave
-- 
View this message in context: 
http://old.nabble.com/Isn%27t-listing-a-dependency-supposed-to-download-that-JAR-file-into-your-WEB-INF-lib-folder--tp26421497p26421497.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Re: ejb-jar plug-in - Can we add dependency jars to ejb-jar.jar

2009-11-19 Thread Stephen Connolly
the jar spec does not support jar files within jar files (technically  
Java's URL support only goes one level deep: eg jar:url/to/file!path/ 
in/jar is allowed, but jar:jar:url/to/file!path/in/jar!path/in/jar is  
not) so while you could copy the jar files inside your ejb jar,  
nothing will be loaded from it


what you can do is explode your dependencies into your jar. there are  
two tools you can use for this: dependency:unpack-dependencies or the  
maven-shade-plugin


Sent from my [rhymes with tryPod] ;-)

On 19 Nov 2009, at 19:00, "Medishetty, Rajendar" > wrote:



Hi,

I'm using ejb-jar plugin to generate the ejb-jar.jar.

I have some library jars, which are only used by this ejbModule. So  
I want them to be packaged inside ejb-jar.jar file only and I don't  
want them to place them in ear lib directory.
I couldn't find anything with ejb-jar plug-in to package these jars  
into ejb-jar.jar file.


Is there any way to do that.

Thanks,
Rajendar



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



ejb-jar plug-in - Can we add dependency jars to ejb-jar.jar

2009-11-19 Thread Medishetty, Rajendar
Hi,

I'm using ejb-jar plugin to generate the ejb-jar.jar.

I have some library jars, which are only used by this ejbModule. So I want them 
to be packaged inside ejb-jar.jar file only and I don't want them to place them 
in ear lib directory.
I couldn't find anything with ejb-jar plug-in to package these jars into 
ejb-jar.jar file.

Is there any way to do that.

Thanks,
Rajendar



RE: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

2009-11-19 Thread Jamie Whitehouse
Many of the dependency plugin goals are reactor aware, but dependency:tree 
isn't.  I'm not too sure why, but you could search the issue tracker and if 
there's no issue for this file one.

-Original Message-
From: Jonathan Gold [mailto:jgold...@gmail.com] 
Sent: Thursday, November 19, 2009 3:00 PM
To: users@maven.apache.org
Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

Jamie --

Thanks for trying it out, and for the explanation. This makes sense in terms of 
why things are happening, so that's nice.

I'm not familiar with the dependency plugin developers (are you one?), and 
wonder if having the dependency plugin be reactor-aware is something they would 
consider? Perhaps its an old tired discussion and the decision to build that 
plugin the way it is is said and done.

Thanks for your help!

jon

On Thu, Nov 19, 2009 at 11:43:33AM -0800, Jamie Whitehouse wrote:
> What maven commands did you issue to test this?
> 
> I used the attached project and here's the results.
> 1) extract zip
> 2) mvn dependency:tree
>   failed due to dependency resolution
> 3) mvn clean install
> 4) mvn dependency:tree
>   see the tree output
> 
> I think you're misunderstanding how the local maven repo is used and the 
> affect reactor builds and plugins that are reactor aware vs not.  AFAIK the 
> dependency:tree goal is not reactor aware.  It needs to resolve artifacts 
> from the local repo (or download from remote repos if not present locally).  
> Since you haven't mvn installed these into your local repo the tree goal 
> states that the artifact is missing.
> 
> The compile goal is reactor aware, and hence if you invoke mvn compile it 
> determines the correct order in your multi-module build in order for mod_b to 
> resolve the reference to mod_a.  To test this reverse the order of the module 
> definitions in the root pom and see that the reactor summary builds mod_a 
> first despite the modules list having mod_b first.
> 
> If you want to simulate what dependency:tree does using the compile goal, 
> just try to compile mod_b on it's own, in it's own sub module (e.g. 
> c:\maven-repro1\mod_b> mvn compile ), you'll get the same error about not 
> being able to resolve dependencies.
> 
> Hope that helps.
> Jamie.
> 
> -Original Message-
> From: Jonathan Gold [mailto:jgold...@gmail.com]
> Sent: Thursday, November 19, 2009 12:52 PM
> To: users@maven.apache.org
> Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?
> 
> Brian --
> 
> Thanks for your help so far. I did put together a very small sample project 
> that will repro what I'm seeing (attached as a zip). Just run 'mvn 
> dependency:tree'
> in the root of the project and see if you get the same error (mod_a is not 
> found, required by mod_b). It does compile fine.
> 
> I'll be interested to see if you get the same results, or have some insights.
> It's totally likely that I'm not setting my poms up correctly.
> 
> Thanks for any help you can give!
> 
> jon
> 
> On Wed, Nov 18, 2009 at 05:53:34PM -0500, Brian Fox wrote:
> > This is not related. The dependency plugin has some issues resolving 
> > things from the reactor and ranges in the following goals only:
> > copy
> > unpack
> > go-offline
> > resolve-plugins
> > 
> > 
> > All the other goals set @requiresDependencyResolution test which 
> > will cause Maven to resolve all dependencies prior to the plugin running.
> > So if you're seeing some error, it's happening in the core. Provide 
> > a sample project and/or some debug output and we might be able to 
> > tell what the problem is.
> > 
> > 
> > On Wed, Nov 18, 2009 at 12:59 PM, Stevo Slavić  wrote:
> > > Likely because dependency plugin has bugs, and I'm suspecting that 
> > > your issue is similar/related to this 
> > > one already reported.
> > >
> > > But it's odd that it doesn't fail for you at module mod_c, as 
> > > build reactor should have ordered mod_c to be built/processed 
> > > before mod_d. Just guessing, maybe this mojo doesn't use maven 
> > > reactor at all, and probably mod_c is ordered in list of modules in your 
> > > parent module after mod_d.
> > >
> > > Regards,
> > > Stevo.
> > >
> > > On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold  wrote:
> > >
> > >> Hi --
> > >>
> > >> I'm trying to track down some other depdendency issues in my 
> > >> project using dependencies:tree, but am getting errors that a module 
> > >> isn't found.
> > >>
> > >> I have my project set up with a parent pom and a list of modules, 
> > >> each referencing the parent, etc. Essentially, I have this:
> > >>
> > >>    pom.xml # parent, references mods a, b, c, d in 
> > >>    mod_a/pom.xml # module, no module dependencies
> > >>    mod_b/pom.xml # module, no module dependencies
> > >>    mod_c/pom.xml # module, declared dependency on mod_b
> > >>    mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, 
> > >> mod_c
> > >>
> > >> From the root

Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

2009-11-19 Thread Jonathan Gold
Jamie --

Thanks for trying it out, and for the explanation. This makes sense in terms of
why things are happening, so that's nice.

I'm not familiar with the dependency plugin developers (are you one?), and
wonder if having the dependency plugin be reactor-aware is something they would
consider? Perhaps its an old tired discussion and the decision to build that
plugin the way it is is said and done.

Thanks for your help!

jon

On Thu, Nov 19, 2009 at 11:43:33AM -0800, Jamie Whitehouse wrote:
> What maven commands did you issue to test this?
> 
> I used the attached project and here's the results.
> 1) extract zip
> 2) mvn dependency:tree
>   failed due to dependency resolution
> 3) mvn clean install
> 4) mvn dependency:tree
>   see the tree output
> 
> I think you're misunderstanding how the local maven repo is used and the 
> affect reactor builds and plugins that are reactor aware vs not.  AFAIK the 
> dependency:tree goal is not reactor aware.  It needs to resolve artifacts 
> from the local repo (or download from remote repos if not present locally).  
> Since you haven't mvn installed these into your local repo the tree goal 
> states that the artifact is missing.
> 
> The compile goal is reactor aware, and hence if you invoke mvn compile it 
> determines the correct order in your multi-module build in order for mod_b to 
> resolve the reference to mod_a.  To test this reverse the order of the module 
> definitions in the root pom and see that the reactor summary builds mod_a 
> first despite the modules list having mod_b first.
> 
> If you want to simulate what dependency:tree does using the compile goal, 
> just try to compile mod_b on it's own, in it's own sub module (e.g. 
> c:\maven-repro1\mod_b> mvn compile ), you'll get the same error about not 
> being able to resolve dependencies.
> 
> Hope that helps.
> Jamie.
> 
> -Original Message-
> From: Jonathan Gold [mailto:jgold...@gmail.com] 
> Sent: Thursday, November 19, 2009 12:52 PM
> To: users@maven.apache.org
> Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?
> 
> Brian --
> 
> Thanks for your help so far. I did put together a very small sample project 
> that will repro what I'm seeing (attached as a zip). Just run 'mvn 
> dependency:tree'
> in the root of the project and see if you get the same error (mod_a is not 
> found, required by mod_b). It does compile fine.
> 
> I'll be interested to see if you get the same results, or have some insights.
> It's totally likely that I'm not setting my poms up correctly.
> 
> Thanks for any help you can give!
> 
> jon
> 
> On Wed, Nov 18, 2009 at 05:53:34PM -0500, Brian Fox wrote:
> > This is not related. The dependency plugin has some issues resolving 
> > things from the reactor and ranges in the following goals only:
> > copy
> > unpack
> > go-offline
> > resolve-plugins
> > 
> > 
> > All the other goals set @requiresDependencyResolution test which will 
> > cause Maven to resolve all dependencies prior to the plugin running.
> > So if you're seeing some error, it's happening in the core. Provide a 
> > sample project and/or some debug output and we might be able to tell 
> > what the problem is.
> > 
> > 
> > On Wed, Nov 18, 2009 at 12:59 PM, Stevo Slavić  wrote:
> > > Likely because dependency plugin has bugs, and I'm suspecting that 
> > > your issue is similar/related to this 
> > > one already reported.
> > >
> > > But it's odd that it doesn't fail for you at module mod_c, as build 
> > > reactor should have ordered mod_c to be built/processed before 
> > > mod_d. Just guessing, maybe this mojo doesn't use maven reactor at 
> > > all, and probably mod_c is ordered in list of modules in your parent 
> > > module after mod_d.
> > >
> > > Regards,
> > > Stevo.
> > >
> > > On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold  wrote:
> > >
> > >> Hi --
> > >>
> > >> I'm trying to track down some other depdendency issues in my 
> > >> project using dependencies:tree, but am getting errors that a module 
> > >> isn't found.
> > >>
> > >> I have my project set up with a parent pom and a list of modules, 
> > >> each referencing the parent, etc. Essentially, I have this:
> > >>
> > >>    pom.xml # parent, references mods a, b, c, d in 
> > >>    mod_a/pom.xml # module, no module dependencies
> > >>    mod_b/pom.xml # module, no module dependencies
> > >>    mod_c/pom.xml # module, declared dependency on mod_b
> > >>    mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, 
> > >> mod_c
> > >>
> > >> From the root workspace directory, I can run things like 'compile' 
> > >> or 'jar:jar'
> > >> just fine, but for some reason 'dependencies:tree' is failing when 
> > >> it gets to mod_d, complaining that it can't find mod_c.
> > >>
> > >> Any ideas what I'm doing wrong?
> > >>
> > >> jon
> > >>
> > >> ---
> > >> -- To unsubscribe, e-mail: users-unsubscr...@maven.a

RE: Putting a Release in the Repository

2009-11-19 Thread Neil Chaudhuri
I have done those things, but I get the following error:

[INFO] [INFO] Cannot execute mojo: clean. It requires a project with an 
existing pom.xml, but the build is not using one.

I thought that error only occurred when the URL to the repo was incorrect. 
Since I am able to do a release:prepare and see the project tagged in SVN, I 
imagine that isn't the case.

It occurred to me that this could be a flatness issue. My release in SVN looks 
like this:

myapp-0.8.1
--parent
--persistence
--services

Each of these represents a module with its own pom. Shockingly, parent is the 
parent module for the others. There is no pom at the myapp-0.8.1 level, so that 
would explain the error.

Because of the flatness issue, I had to add configure the release plugin in the 
following fashion for it to work:


${basedir}/..
false
clean install
clean install
-Dmaven.test.skip
svn:///data/svn/project/tags  
true



Given this setup, how can I do the release? Any insight is appreciated.

Thanks.



-Original Message-
From: Stevo Slavić [mailto:ssla...@gmail.com] 
Sent: Thursday, November 19, 2009 2:22 PM
To: Maven Users List
Subject: Re: Putting a Release in the Repository

http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin

http://www.vineetmanohar.com/2009/10/23/how-to-automate-project-versioning-and-release-with-maven/

Regards,
Stevo.

On Thu, Nov 19, 2009 at 8:19 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> mvn release:perform
> after the prepare
>
> Sent from my [rhymes with tryPod] ;-)
>
>
> On 19 Nov 2009, at 19:11, "Neil Chaudhuri" 
> wrote:
>
>  I am using the prepare goal of the Maven Release Plugin to publish a
>> release in SVN. The result of course is that the poms in the trunk and
>> in my local copy are updated to the next version snapshot. What I want
>> to do is to take the release in SVN and publish it to my local Nexus
>> repository in the releases portion of the site. I am doing the same for
>> snapshots by using the Maven Deploy Plugin.
>>
>>
>>
>> I suppose my question is how can I get the Maven Release and Deploy
>> Plugins to work in tandem so that I can release something to SVN and
>> then have it be deployed to my local Nexus repository.
>>
>>
>>
>> Thanks.
>>
>>
>>
>>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


RE: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

2009-11-19 Thread Jamie Whitehouse
What maven commands did you issue to test this?

I used the attached project and here's the results.
1) extract zip
2) mvn dependency:tree
  failed due to dependency resolution
3) mvn clean install
4) mvn dependency:tree
  see the tree output

I think you're misunderstanding how the local maven repo is used and the affect 
reactor builds and plugins that are reactor aware vs not.  AFAIK the 
dependency:tree goal is not reactor aware.  It needs to resolve artifacts from 
the local repo (or download from remote repos if not present locally).  Since 
you haven't mvn installed these into your local repo the tree goal states that 
the artifact is missing.

The compile goal is reactor aware, and hence if you invoke mvn compile it 
determines the correct order in your multi-module build in order for mod_b to 
resolve the reference to mod_a.  To test this reverse the order of the module 
definitions in the root pom and see that the reactor summary builds mod_a first 
despite the modules list having mod_b first.

If you want to simulate what dependency:tree does using the compile goal, just 
try to compile mod_b on it's own, in it's own sub module (e.g. 
c:\maven-repro1\mod_b> mvn compile ), you'll get the same error about not being 
able to resolve dependencies.

Hope that helps.
Jamie.

-Original Message-
From: Jonathan Gold [mailto:jgold...@gmail.com] 
Sent: Thursday, November 19, 2009 12:52 PM
To: users@maven.apache.org
Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

Brian --

Thanks for your help so far. I did put together a very small sample project 
that will repro what I'm seeing (attached as a zip). Just run 'mvn 
dependency:tree'
in the root of the project and see if you get the same error (mod_a is not 
found, required by mod_b). It does compile fine.

I'll be interested to see if you get the same results, or have some insights.
It's totally likely that I'm not setting my poms up correctly.

Thanks for any help you can give!

jon

On Wed, Nov 18, 2009 at 05:53:34PM -0500, Brian Fox wrote:
> This is not related. The dependency plugin has some issues resolving 
> things from the reactor and ranges in the following goals only:
> copy
> unpack
> go-offline
> resolve-plugins
> 
> 
> All the other goals set @requiresDependencyResolution test which will 
> cause Maven to resolve all dependencies prior to the plugin running.
> So if you're seeing some error, it's happening in the core. Provide a 
> sample project and/or some debug output and we might be able to tell 
> what the problem is.
> 
> 
> On Wed, Nov 18, 2009 at 12:59 PM, Stevo Slavić  wrote:
> > Likely because dependency plugin has bugs, and I'm suspecting that 
> > your issue is similar/related to this 
> > one already reported.
> >
> > But it's odd that it doesn't fail for you at module mod_c, as build 
> > reactor should have ordered mod_c to be built/processed before 
> > mod_d. Just guessing, maybe this mojo doesn't use maven reactor at 
> > all, and probably mod_c is ordered in list of modules in your parent module 
> > after mod_d.
> >
> > Regards,
> > Stevo.
> >
> > On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold  wrote:
> >
> >> Hi --
> >>
> >> I'm trying to track down some other depdendency issues in my 
> >> project using dependencies:tree, but am getting errors that a module isn't 
> >> found.
> >>
> >> I have my project set up with a parent pom and a list of modules, 
> >> each referencing the parent, etc. Essentially, I have this:
> >>
> >>    pom.xml # parent, references mods a, b, c, d in 
> >>    mod_a/pom.xml # module, no module dependencies
> >>    mod_b/pom.xml # module, no module dependencies
> >>    mod_c/pom.xml # module, declared dependency on mod_b
> >>    mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, 
> >> mod_c
> >>
> >> From the root workspace directory, I can run things like 'compile' 
> >> or 'jar:jar'
> >> just fine, but for some reason 'dependencies:tree' is failing when 
> >> it gets to mod_d, complaining that it can't find mod_c.
> >>
> >> Any ideas what I'm doing wrong?
> >>
> >> jon
> >>
> >> ---
> >> -- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


---
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain 
confidential and proprietary information of Alcatel-Lucent and/or its 
affiliated entities. Access by the intended recipient only is authorized. Any 
liability arising from any party acting, or refraini

Re: Putting a Release in the Repository

2009-11-19 Thread Stevo Slavić
http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin

http://www.vineetmanohar.com/2009/10/23/how-to-automate-project-versioning-and-release-with-maven/

Regards,
Stevo.

On Thu, Nov 19, 2009 at 8:19 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> mvn release:perform
> after the prepare
>
> Sent from my [rhymes with tryPod] ;-)
>
>
> On 19 Nov 2009, at 19:11, "Neil Chaudhuri" 
> wrote:
>
>  I am using the prepare goal of the Maven Release Plugin to publish a
>> release in SVN. The result of course is that the poms in the trunk and
>> in my local copy are updated to the next version snapshot. What I want
>> to do is to take the release in SVN and publish it to my local Nexus
>> repository in the releases portion of the site. I am doing the same for
>> snapshots by using the Maven Deploy Plugin.
>>
>>
>>
>> I suppose my question is how can I get the Maven Release and Deploy
>> Plugins to work in tandem so that I can release something to SVN and
>> then have it be deployed to my local Nexus repository.
>>
>>
>>
>> Thanks.
>>
>>
>>
>>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


Re: Putting a Release in the Repository

2009-11-19 Thread Stephen Connolly

mvn release:perform
after the prepare

Sent from my [rhymes with tryPod] ;-)

On 19 Nov 2009, at 19:11, "Neil Chaudhuri"  
 wrote:



I am using the prepare goal of the Maven Release Plugin to publish a
release in SVN. The result of course is that the poms in the trunk and
in my local copy are updated to the next version snapshot. What I want
to do is to take the release in SVN and publish it to my local Nexus
repository in the releases portion of the site. I am doing the same  
for

snapshots by using the Maven Deploy Plugin.



I suppose my question is how can I get the Maven Release and Deploy
Plugins to work in tandem so that I can release something to SVN and
then have it be deployed to my local Nexus repository.



Thanks.





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



Putting a Release in the Repository

2009-11-19 Thread Neil Chaudhuri
I am using the prepare goal of the Maven Release Plugin to publish a
release in SVN. The result of course is that the poms in the trunk and
in my local copy are updated to the next version snapshot. What I want
to do is to take the release in SVN and publish it to my local Nexus
repository in the releases portion of the site. I am doing the same for
snapshots by using the Maven Deploy Plugin.

 

I suppose my question is how can I get the Maven Release and Deploy
Plugins to work in tandem so that I can release something to SVN and
then have it be deployed to my local Nexus repository.

 

Thanks.

 



Project Builds

2009-11-19 Thread Joel Schuster
It seems that Maven good about particular artifacts, but I can't seem to figure 
out how to do multiple projects into one distribution...

I have various OSGi based applications. The core OSGi framework with all the 
bundles that all our projects use in common are included in one project. There 
are a number of bundles that are 3rd party and a number that are internal to 
our company.

How would I use Maven to not just help me control single projects, but rather 
the entire execution environment including all the runtime dependencies, 
configuration files and even the startup scripts?

Is there a documented example to help me along? I don't see any documentation 
within Maven that would help me wrap this problem.



Joel Schuster
Senior Software Engineer
NAVSYS Corporation
14960 Woodcarver Road, Colorado Springs, CO 80921
719-481-4877





Re: Maven not taking the latest snapshot

2009-11-19 Thread Brian Fox
It should get updated yes. It is possible that your teamcity instance
is also building and producing this jar via some other build?

On Thu, Nov 19, 2009 at 11:37 AM, Yury Kudryashov
 wrote:
> Thank you for your response, Brian. Unfortunately upgrading to 2.2.1 did not
> help - today the problem was reproduced again.
>
> After looking at the local repository on the build server we have noticed
> that there is a snapshot version without the timestamp part in the name.
> This version is much older than any of the latest snapshots and it seems
> Maven takes exactly this old version.
>
> Here's a dump of the local repository for one of the artifacts:
>
> -rw-r--r-- 1 teamcity teamcity 1178041 2009-11-18 18:26
> tobj-TRUNK-20091118.152629-342.jar
> -rw-r--r-- 1 teamcity teamcity     404 2009-11-18 18:26
> tobj-TRUNK-20091118.152629-342.pom
> -rw-r--r-- 1 teamcity teamcity 1178195 2009-11-19 15:58
> tobj-TRUNK-20091119.125835-343.jar
> -rw-r--r-- 1 teamcity teamcity     404 2009-11-19 15:58
> tobj-TRUNK-20091119.125835-343.pom
> -rw-r--r-- 1 teamcity teamcity 1178195 2009-11-19 16:49
> tobj-TRUNK-20091119.134950-344.jar
> -rw-r--r-- 1 teamcity teamcity     404 2009-11-19 16:50
> tobj-TRUNK-20091119.134950-344.pom
> -rw-r--r-- 1 teamcity teamcity 1171191 2009-11-17 22:15
> tobj-TRUNK-SNAPSHOT.jar
> -rw-r--r-- 1 teamcity teamcity     404 2009-11-17 22:15
> tobj-TRUNK-SNAPSHOT.pom
>
>
> As you may see there is a snapshot as of 11-19
> (tobj-TRUNK-20091119.134950-344.jar) but the tobj-TRUNK-SNAPSHOT.jar is much
> older. Should this "default" snapshot be updated automatically? It looks
> like it should, but it does not. Can this be a configuration problem?
>
> --
> Yury Kudryashov
>
>
> -Original Message-
> From: Brian Fox [mailto:bri...@infinity.nu]
> Sent: Tuesday, November 17, 2009 8:36 PM
> To: Maven Users List
> Subject: Re: Maven not taking the latest snapshot
>
> First, I would not use 2.1.0, use 2.0.10 or 2.2.1 instead. I'm fairly
> certain that -U works properly in those versions. (2.1.0 shouldn't be
> used at all, there were lots of issues there and we went right to
> 2.2.x)
>
> On Tue, Nov 17, 2009 at 6:24 AM, Yury Kudryashov
>  wrote:
>> Hello,
>>
>> We have a set of products some of them depending on the others. We use
> Maven
>> to control dependencies and a continuous integration server to check
> whether
>> the changes are compatible.
>>
>> Continuous integration server first builds and deploys (to local
> Nexus-based
>> repository) snapshot versions of the parent component and then builds the
>> dependent components (which take and use the parent SNAPSHOTS).
>>
>> The problem is that sometimes the continuous integration server caches a
>> SNAPSHOT artifact in the local repository and then refuses to take newer
> one
>> from the remote repository. This leads to failing builds. This happens
>> periodically, but not all the time. Deletion of the local repository on
> the
>> build server helps, but it is very inconvenient.
>>
>> Builds are run with the -U switch, but it seems to have no effect.
>>
>> We're using Maven 2.1.0 on Ubuntu.
>>
>> Please advise what can be the cause of the problem.
>>
>> Thank you.
>>
>>
>> --
>> Yury Kudryashov
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

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



Re: How do I prevent maven from searching my own artifacts in public repositories ?

2009-11-19 Thread Wayne Fay
> Anyway, hope that helps, and maybe some more experienced maveners can shed 
> more
> light.

Maven needs poms to know the dependencies etc for a given artifact, right??

If the poms aren't there, it can only assume your artifacts have zero
dependencies, and most of the time that is a poor assumption, right?

So missing poms are a big problem for Maven in general. Thus, it will
always try to find poms if they are missing.

Wayne

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



Re: How do I prevent maven from searching my own artifacts in public repositories ?

2009-11-19 Thread Jonathan Gold
Torsten --

I had the same problem with poms I installed locally using the
install:install-file task. Once I added '-DgeneratePom=true' to that command, I
noticed that maven no longer attempted to search the public repos. I'm new to
maven, so I can't confirm why this happened, but I suspect it had to do with the
fact that, without a pom (generated or otherwise) along with my local artifact,
maven did the correct thing and attempted to check in the remote repos whether
the version I had locally was most up to date.

Anyway, hope that helps, and maybe some more experienced maveners can shed more
light.

jon

On Thu, Nov 19, 2009 at 03:15:23PM +0100, TorstenKarusseit wrote:
> Hi, may be a simple question:
> 
> How do I prevent maven from searching my own artifacts in public repositories 
> ?
> While I playing around with my pom files there are often situations
> where maven uselessly disturbs externel maven repositories.
> Which I want to prevent if possible.
> 
> Thank you.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

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



Explanation for maven release:branch parameters

2009-11-19 Thread Jozsef Zsido
Hi,

On page:
http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html
there is a remark at the bottom to control the branch and current versions
with a command:

mvn --batch-mode release:branch -DbranchName=my-branch-1.2
-Dproject.rel.org.myCompany:projectA=1.2 \
 -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT


-Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT seems to have a mandatory
part "project.dev." then the artifact groupID: "org.myCompany" and then the
artifact id: "projectA"
I'm trying to use this command for may case but simply creates the branch
and increments the work version by 1 and leaves untouched the branch
version.

What I'm trying to accomplish is to set manually the working version by
incrementing the y part of the x.y.z-SNAPSHOT version format and to leave
unchanged the branch version.

Any idea how should I use the plugin?

Regards,
Jozsef


RE: Maven not taking the latest snapshot

2009-11-19 Thread Yury Kudryashov
Thank you for your response, Brian. Unfortunately upgrading to 2.2.1 did not
help - today the problem was reproduced again.

After looking at the local repository on the build server we have noticed
that there is a snapshot version without the timestamp part in the name.
This version is much older than any of the latest snapshots and it seems
Maven takes exactly this old version.

Here's a dump of the local repository for one of the artifacts:

-rw-r--r-- 1 teamcity teamcity 1178041 2009-11-18 18:26
tobj-TRUNK-20091118.152629-342.jar 
-rw-r--r-- 1 teamcity teamcity 404 2009-11-18 18:26
tobj-TRUNK-20091118.152629-342.pom 
-rw-r--r-- 1 teamcity teamcity 1178195 2009-11-19 15:58
tobj-TRUNK-20091119.125835-343.jar 
-rw-r--r-- 1 teamcity teamcity 404 2009-11-19 15:58
tobj-TRUNK-20091119.125835-343.pom 
-rw-r--r-- 1 teamcity teamcity 1178195 2009-11-19 16:49
tobj-TRUNK-20091119.134950-344.jar 
-rw-r--r-- 1 teamcity teamcity 404 2009-11-19 16:50
tobj-TRUNK-20091119.134950-344.pom 
-rw-r--r-- 1 teamcity teamcity 1171191 2009-11-17 22:15
tobj-TRUNK-SNAPSHOT.jar 
-rw-r--r-- 1 teamcity teamcity 404 2009-11-17 22:15
tobj-TRUNK-SNAPSHOT.pom


As you may see there is a snapshot as of 11-19
(tobj-TRUNK-20091119.134950-344.jar) but the tobj-TRUNK-SNAPSHOT.jar is much
older. Should this "default" snapshot be updated automatically? It looks
like it should, but it does not. Can this be a configuration problem?

--
Yury Kudryashov


-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu] 
Sent: Tuesday, November 17, 2009 8:36 PM
To: Maven Users List
Subject: Re: Maven not taking the latest snapshot

First, I would not use 2.1.0, use 2.0.10 or 2.2.1 instead. I'm fairly
certain that -U works properly in those versions. (2.1.0 shouldn't be
used at all, there were lots of issues there and we went right to
2.2.x)

On Tue, Nov 17, 2009 at 6:24 AM, Yury Kudryashov
 wrote:
> Hello,
>
> We have a set of products some of them depending on the others. We use
Maven
> to control dependencies and a continuous integration server to check
whether
> the changes are compatible.
>
> Continuous integration server first builds and deploys (to local
Nexus-based
> repository) snapshot versions of the parent component and then builds the
> dependent components (which take and use the parent SNAPSHOTS).
>
> The problem is that sometimes the continuous integration server caches a
> SNAPSHOT artifact in the local repository and then refuses to take newer
one
> from the remote repository. This leads to failing builds. This happens
> periodically, but not all the time. Deletion of the local repository on
the
> build server helps, but it is very inconvenient.
>
> Builds are run with the -U switch, but it seems to have no effect.
>
> We're using Maven 2.1.0 on Ubuntu.
>
> Please advise what can be the cause of the problem.
>
> Thank you.
>
>
> --
> Yury Kudryashov
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

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


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



findbugs-plugin: Premature end of file.

2009-11-19 Thread Bruno Marti

I'm getting an error in maven-findbugs-plugin on site generation:
Environment: win xp, java 1.6.0_16, maven 2.2.1, findbugs-plugin
2.2/2.1/2.0.1


[INFO] Generating "FindBugs Report" report.
[INFO]   Plugin Artifacts to be added
->[org.apache.maven.reporting:maven-reporting-impl:jar:2.0:runtime,
org.codehaus.plexus:plexus-utils:jar:1.5.1:runtime,
commons-validator:commons-validator:jar:1.1.4:runtime,
oro:oro:jar:2.0.7:runtime, doxia:doxia-core:jar:1.0-alpha-4:runtime,
org.apache.maven.shared:maven-doxia-tools:jar:1.0:runtime,
commons-io:commons-io:jar:1.4:runtime,
org.apache.maven.doxia:doxia-decoration-model:jar:1.0-alpha-11:runtime,
org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7:runtime,
com.google.code.findbugs:findbugs-ant:jar:1.3.9:runtime,
com.google.code.findbugs:findbugs:jar:1.3.9:runtime,
com.google.code.findbugs:bcel:jar:1.3.9:runtime,
com.google.code.findbugs:jsr305:jar:1.3.9:runtime,
com.google.code.findbugs:jFormatString:jar:1.3.9:runtime,
com.google.code.findbugs:annotations:jar:1.3.9:runtime,
dom4j:dom4j:jar:1.6.1:runtime, xml-apis:xml-apis:jar:1.0.b2:runtime,
jaxen:jaxen:jar:1.1.1:runtime, jdom:jdom:jar:1.0:runtime,
xerces:xercesImpl:jar:2.6.2:runtime, xom:xom:jar:1.0:runtime,
xerces:xmlParserAPIs:jar:2.6.2:runtime, xalan:xalan:jar:2.6.0:runtime,
com.ibm.icu:icu4j:jar:2.6.1:runtime, asm:asm:jar:3.1:runtime,
asm:asm-analysis:jar:3.1:runtime, asm:asm-tree:jar:3.1:runtime,
asm:asm-commons:jar:3.1:runtime, asm:asm-util:jar:3.1:runtime,
asm:asm-xml:jar:3.1:runtime, commons-lang:commons-lang:jar:2.4:runtime,
jgoodies:plastic:jar:1.2.0:runtime,
org.codehaus.groovy.maven:gmaven-mojo:jar:1.0-rc-3:runtime,
org.codehaus.groovy.maven.runtime:gmaven-runtime-api:jar:1.0-rc-3:runtime,
org.codehaus.groovy.maven.feature:gmaven-feature-api:jar:1.0-rc-3:runtime,
org.codehaus.groovy.maven.runtime:gmaven-runtime-default:jar:1.0-rc-3:runtime,
org.slf4j:slf4j-api:jar:1.5.0:runtime,
org.codehaus.groovy.maven.runtime:gmaven-runtime-1.5:jar:1.0-rc-3:runtime,
org.codehaus.groovy.maven.feature:gmaven-feature-support:jar:1.0-rc-3:runtime,
org.codehaus.groovy.maven.runtime:gmaven-runtime-support:jar:1.0-rc-3:runtime,
org.codehaus.groovy.maven:gmaven-common:jar:1.0-rc-3:runtime,
com.thoughtworks.qdox:qdox:jar:1.6.3:runtime,
org.codehaus.groovy:groovy-all-minimal:jar:1.5.6:runtime,
org.apache.ant:ant:jar:1.7.1:runtime,
org.apache.ant:ant-launcher:jar:1.7.1:runtime,
jline:jline:jar:0.9.94:runtime,
org.codehaus.plexus:plexus-resources:jar:1.0-alpha-4:runtime,
org.apache.maven.reporting:maven-reporting-api:jar:2.0.8:runtime]
[INFO]   AuxClasspath is
->C:\ProgrammeWEB\.m2\repository\org\apache\maven\reporting\maven-reporting-impl\2.0\maven-reporting-impl-2.0.jar;C:\ProgrammeWEB\.m2\repository\org\codehaus\plexus\plexus-utils\1.5.1\plexus-utils-1.5.1.jar;C:\ProgrammeWEB\.m2\repository\commons-validator\commons-validator\1.1.4\commons-validator-1.1.4.jar;C:\ProgrammeWEB\.m2\repository\oro\oro\2.0.7\oro-2.0.7.jar;C:\ProgrammeWEB\.m2\repository\doxia\doxia-core\1.0-alpha-4\doxia-core-1.0-alpha-4.jar;C:\ProgrammeWEB\.m2\repository\org\apache\maven\shared\maven-doxia-tools\1.0\maven-doxia-tools-1.0.jar;C:\ProgrammeWEB\.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.jar;C:\ProgrammeWEB\.m2\repository\org\apache\maven\doxia\doxia-decoration-model\1.0-alpha-11\doxia-decoration-model-1.0-alpha-11.jar;C:\ProgrammeWEB\.m2\repository\org\codehaus\plexus\plexus-i18n\1.0-beta-7\plexus-i18n-1.0-beta-7.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\findbugs-ant\1.3.9\findbugs-ant-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\findbugs\1.3.9\findbugs-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\bcel\1.3.9\bcel-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\jsr305\1.3.9\jsr305-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\jFormatString\1.3.9\jFormatString-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\annotations\1.3.9\annotations-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar;C:\ProgrammeWEB\.m2\repository\xml-apis\xml-apis\1.0.b2\xml-apis-1.0.b2.jar;C:\ProgrammeWEB\.m2\repository\jaxen\jaxen\1.1.1\jaxen-1.1.1.jar;C:\ProgrammeWEB\.m2\repository\jdom\jdom\1.0\jdom-1.0.jar;C:\ProgrammeWEB\.m2\repository\xerces\xercesImpl\2.6.2\xercesImpl-2.6.2.jar;C:\ProgrammeWEB\.m2\repository\xom\xom\1.0\xom-1.0.jar;C:\ProgrammeWEB\.m2\repository\xerces\xmlParserAPIs\2.6.2\xmlParserAPIs-2.6.2.jar;C:\ProgrammeWEB\.m2\repository\xalan\xalan\2.6.0\xalan-2.6.0.jar;C:\ProgrammeWEB\.m2\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm\3.1\asm-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-analysis\3.1\asm-analysis-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-tree\3.1\asm-tree-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-commons\3.1\asm-commons-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-util\3.1\asm-util-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-xml\3.1\asm-xml-3.1.jar;

Re: How do I prevent maven from searching my own artifacts in public repositories ?

2009-11-19 Thread Anders Hammar
Different solutions:
1) Make sure your internal repo is searched before any external repos (done
on Maven client side).
2) Use a repo manager (e.g. Nexus) that can handle routing rules like this
for you.

Solution 1) would require some trial and error. I've done this through repo
definitions in profiles in settings.xml, and I recall that the order the
profiles were defined mattered. However, I believe this could different
between Maven versions.
I think 2) is the way to go if privacy is important to you (i.e. not letting
external parties know what internal artifacts you're working on).

/Anders

On Thu, Nov 19, 2009 at 15:15, TorstenKarusseit wrote:

> Hi, may be a simple question:
>
> How do I prevent maven from searching my own artifacts in public
> repositories ?
> While I playing around with my pom files there are often situations
> where maven uselessly disturbs externel maven repositories.
> Which I want to prevent if possible.
>
> Thank you.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


maven-assembly-plugin: referencing assembly id from component descriptor

2009-11-19 Thread Stevo Slavić
Hello Maven users,

Is there a way to reference assembly id from component descriptor? Is it
exposed as some property?

Regards,
Stevo.


How do I prevent maven from searching my own artifacts in public repositories ?

2009-11-19 Thread TorstenKarusseit

Hi, may be a simple question:

How do I prevent maven from searching my own artifacts in public 
repositories ?

While I playing around with my pom files there are often situations
where maven uselessly disturbs externel maven repositories.
Which I want to prevent if possible.

Thank you.

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



Re: Problem with maven-release-plugin

2009-11-19 Thread Martin Schayna
Ah, sorry. I looked and it seems that I was wrong. We have the version 
specified in each pom.xml, even in modules. But actually that is not 
problem, because only maven-release-plugin does change version, not 
people. Hence it that I did not remember right.

Martin Schayna


Peter Niederwieser wrote:

Are we talking about the same thing? Do you also have a module with a 
dependency on your OWN maven plugin located in another module that is part of 
the same release?

On 19.11.2009, at 14:00, Martin Schayna wrote:

  

We have same scenario. Release plugin only warns "can't change version" on 
dependent projects. Released deliveries are OK.
Martin Schayna

Peter Niederwieser wrote:

In my multi-module project, I have a Maven plugin A and a module B that uses version ${project.version} of A (all modules have the same version number). release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails while processing B because it cannot find version 0.3 of A. Any ideas how to solve this problem? 
Cheers, Peter
 
  

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





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

  


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



Re: Problem with maven-release-plugin

2009-11-19 Thread Peter Niederwieser
Are we talking about the same thing? Do you also have a module with a 
dependency on your OWN maven plugin located in another module that is part of 
the same release?

On 19.11.2009, at 14:00, Martin Schayna wrote:

> We have same scenario. Release plugin only warns "can't change version" on 
> dependent projects. Released deliveries are OK.
> Martin Schayna
> 
> Peter Niederwieser wrote:
>> In my multi-module project, I have a Maven plugin A and a module B that uses 
>> version ${project.version} of A (all modules have the same version number). 
>> release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails 
>> while processing B because it cannot find version 0.3 of A. Any ideas how to 
>> solve this problem? 
>> Cheers, Peter
>>  
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


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



Re: Assembly plugin: specifying an alternative extension name for the assembly

2009-11-19 Thread Joe Hindsley

Hi Graham,

The extension for the assembly is configured with the  element 
of the assembly descriptor. There are only a couple of supported 
formats. My guess is that you'd have to write a custom Archiver to get a 
different extension, but haven't looked under the hood of the assembly 
plugin to know for sure.


More information is here:

http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_assembly

Joe Hindsley


Graham Charters wrote:

Hi,

I'm trying to create a zip file using the assembly plugin, but I'd
like it to have a different extension (not .zip).  I've tried using
, but that still insists on giving the file the .zip
extension.

Is this possible using the assembly plugin, or should I be using something else?

Many thanks for any help.

Regards, Graham.

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



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



Re: Problem with maven-release-plugin

2009-11-19 Thread Martin Schayna
We have same scenario. Release plugin only warns "can't change version" 
on dependent projects. Released deliveries are OK.

Martin Schayna

Peter Niederwieser wrote:
In my multi-module project, I have a Maven plugin A and a module B that uses version ${project.version} of A (all modules have the same version number). release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails while processing B because it cannot find version 0.3 of A. Any ideas how to solve this problem? 

Cheers, 
Peter
  


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



Problem with maven-release-plugin

2009-11-19 Thread Peter Niederwieser
In my multi-module project, I have a Maven plugin A and a module B that uses 
version ${project.version} of A (all modules have the same version number). 
release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails 
while processing B because it cannot find version 0.3 of A. Any ideas how to 
solve this problem? 

Cheers, 
Peter

Re: Problem with maven-release-plugin

2009-11-19 Thread Stevo Slavić
Maybe this  known issue is
related.

Regards,
Stevo.

On Thu, Nov 19, 2009 at 11:50 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Two options:
>
> 1. change your build so that it will work with "clean verify" whenyour
> local repository has been blown away.  Typically this is because you
> are using goals like dependency:copy and not
> dependency:copy-dependencies
>
> 2. change the preparation goals in the release plugin to "clean install".
>
> #2 is a hack, but may be necessary.  In the long run #1 is to be preferred.
>
> -Stephen
>
> 2009/11/19 Peter Niederwieser :
> >
> > In my multi-module project, I have a Maven plugin A and a module B that
> uses
> > version ${project.version} of A (all modules have the same version
> number).
> > release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then
> fails
> > while processing B because it cannot find version 0.3 of A. Any ideas how
> to
> > solve this problem?
> >
> > Cheers,
> > Peter
> > --
> > View this message in context:
> http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


Assembly plugin: specifying an alternative extension name for the assembly

2009-11-19 Thread Graham Charters
Hi,

I'm trying to create a zip file using the assembly plugin, but I'd
like it to have a different extension (not .zip).  I've tried using
, but that still insists on giving the file the .zip
extension.

Is this possible using the assembly plugin, or should I be using something else?

Many thanks for any help.

Regards, Graham.

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



Re: Problem with maven-release-plugin

2009-11-19 Thread Stephen Connolly
Two options:

1. change your build so that it will work with "clean verify" whenyour
local repository has been blown away.  Typically this is because you
are using goals like dependency:copy and not
dependency:copy-dependencies

2. change the preparation goals in the release plugin to "clean install".

#2 is a hack, but may be necessary.  In the long run #1 is to be preferred.

-Stephen

2009/11/19 Peter Niederwieser :
>
> In my multi-module project, I have a Maven plugin A and a module B that uses
> version ${project.version} of A (all modules have the same version number).
> release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails
> while processing B because it cannot find version 0.3 of A. Any ideas how to
> solve this problem?
>
> Cheers,
> Peter
> --
> View this message in context: 
> http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

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



AW: Problem with maven-release-plugin

2009-11-19 Thread Mark Struberg
Peter,

use the  section in the parent pom to pin down the 
versions of the single child modules.

LieGrue,
strub

--- Peter Niederwieser  schrieb am Do, 19.11.2009:

> Von: Peter Niederwieser 
> Betreff: Problem with maven-release-plugin
> An: users@maven.apache.org
> Datum: Donnerstag, 19. November 2009, 11:46
> 
> In my multi-module project, I have a Maven plugin A and a
> module B that uses
> version ${project.version} of A (all modules have the same
> version number).
> release:prepare changes version A from 0.3-SNAPSHOT to 0.3,
> but then fails
> while processing B because it cannot find version 0.3 of A.
> Any ideas how to
> solve this problem?
> 
> Cheers,
> Peter
> -- 
> View this message in context: 
> http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
> Sent from the Maven - Users mailing list archive at
> Nabble.com.
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 




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



Problem with maven-release-plugin

2009-11-19 Thread Peter Niederwieser

In my multi-module project, I have a Maven plugin A and a module B that uses
version ${project.version} of A (all modules have the same version number).
release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then fails
while processing B because it cannot find version 0.3 of A. Any ideas how to
solve this problem?

Cheers,
Peter
-- 
View this message in context: 
http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



An Ant BuildException has occured: java.lang.IllegalAccessError

2009-11-19 Thread Ken Turner

Here's my environment:

Maven version: 2.2.0
Java version: 1.6.0_13
OS name: "linux" version: "2.4.21-58.el" arch: "i386" Family: "unix"
Apache Ant version 1.6.5 compiled on June 2 2005

I'm getting this error:

[INFO] Building trips-types
[INFO] task-segment: [install]
[INFO]

[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/dataarea1/users/builder/TRIPS2/Dev/Java/Projects/trips-types/src/META-INF
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] An Ant BuildException has occured: java.lang.IllegalAccessError:
tried to access method
org.apache.tools.ant.launch.Locator.decodeUri(Ljava/lang/String;)Ljava/lang/String;
from class org.apache.tools.ant.AntClassLoader

However, if I downgrade Maven to version 2.0.9 it runs fine.

Presumably this is a Maven/Ant compatibility thing; can anybody tell me what
I need to do to resolve it?

-- 
View this message in context: 
http://old.nabble.com/An-Ant-BuildException-has-occured%3A-java.lang.IllegalAccessError-tp26421264p26421264.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



[ANN] Maven Checkstyle Plugin 2.4 Released

2009-11-19 Thread Mark Hobson
The Maven team is pleased to announce the release of the Maven
Checkstyle Plugin, version 2.4.

This plugin generates a report on violations of code style and
optionally fails the build if violations are detected.

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

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


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


Release Notes - Maven 2.x Checkstyle Plugin - Version 2.4

** Improvement
* [MCHECKSTYLE-105] - Update to Checkstyle 5.0
* [MCHECKSTYLE-122] - Add Portuguese (Brazil) translation
* [MCHECKSTYLE-124] - Add Swedish translation

** Task
* [MCHECKSTYLE-119] - Review the Doxia Sink calls
* [MCHECKSTYLE-120] - Bump to Doxia 1.0
* [MCHECKSTYLE-125] - Update to maven-reporting-impl-2.0.4.3

Enjoy,

-The Maven team

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