RE: Maven Assembly for MultiModule project

2008-03-07 Thread Brian E. Fox
Check out the free book[1], this can be read in a few hours and should
get you up to speed quickly.

[1] http://www.sonatype.com/book

-Original Message-
From: krishnan.1000 [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 1:14 PM
To: users@maven.apache.org
Subject: Re: Maven Assembly for MultiModule project


Hi Wayne,

I can not help it. I just joined a project to replace a guy who left the
project. So I am on an accelerated learning curve.

Thanks,

Karthik

Wayne Fay wrote:
> 
> It sounds like you're jumping in to complex builds with Maven2 without
> really understanding how things work at a basic level. As an example
> of this, you're running mvn install:install-file etc on what seems to
> be a Maven project -- so you really only need to type "mvn install".
> The same thing goes for your comment about "adding dependencies in all
> the pom.xml even if they have been specified in the parent." So I
> think you've skipped some important steps in your learning process.
> 
> I would go back to the beginning and work your way through Better
> Builds With Maven (free pdf book from devzuz.com) and Maven: The
> Definitive Guide (from sonatype.com). The books are organized such
> that you start out learning how Maven works internally (generally),
> and then they lead through some basic examples and finally take you
> through much more involved examples.
> 
> You should be able to do this in just 1 or 2 days, and I think you
> really need to invest this time now rather than attempting to hack
> your poms and assemblies just to make it work.
> 
> Wayne
> 
> On 3/7/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>>
>>  
>>
>>   
>>maven-compiler-plugin
>>2.1-20080129.223043-7
>>
>>  1.5
>>  1.5
>>
>>  
>>  
>> 
>>org.apache.maven.plugins
>>maven-surefire-plugin
>>2.4
>>
>>  
>>testng.xml
>>  
>>
>>  
>>  
>>maven-assembly-plugin
>>
>>  
>>jar-with-dependencies
>>  
>>  
>>
>>  true
>>  com.jbe.core.Foo
>>
>>  
>>
>>  
>>
>>  
>>
>> 
>>../pom.xml
>>0.1
>>foo-foo
>>foo
>>  
>>
>> I also find that I have to include foo-b in my foo's pom.xml in order
to
>> compile even though, foo-a is dependent on foo-b and therefore must
>> compile
>> foo-b before foo-a.
>> 
>>  
>>  foo
>>  foo-a
>>  ${project.version}
>>  compile
>>
>> 
>>  foo
>>  foo-b
>>  ${project.version}
>>  compile
>> 
>> /dependencies>
>>
>> In addition, I have to add dependencies in all the pom.xml even if
they
>> have
>> been specified in the parent pom.xml.
>>
>> Thanks,
>>
>> Karthik Krishnan
>>
>>
>>
>> krishnan.1000 wrote:
>> >
>> > Hi Wayne,
>> >
>> > I am sorry Wayne. I should have been more specific on the post. To
>> answer
>> > your first comment,  and I do not wish to sound rude, but if I knew
>> what I
>> > was doing wrong, I would not have posted in the first place.
>> >
>> > 2. I am trying to assemble a jar of module Foo and Bar . I wish
that I
>> > create an executable jar with a defined main class and a classpath
>> added
>> > to MANIFEST.MF. So basically i want the to create foo.jar and
bar.jar
>> > containing all the dependencies.
>> >
>> > 3. I find  that if i make the changes in Foo-A or FooB java
classes,
>> and
>> > if i execute a mvn assembly:assembly, it does not build the FOO-A
or
>> FOO-B
>> > in the .m2 repository before building Foo and Bar successfully
again I
>> > have to get around that by doing the following
>> >
>> > mvn install:install-file
>> > -Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar
>> -DgroupId=project
>> > -DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar
-DgeneratePOM=true,
>> the
>> > solution I found by doing a search on one of the posts.
>> >
>> > and again for foo-b. I would like to avoid that and just have mvn
>> > assembly:assembly do all this before creating foo.jar and bar.jar.
>> >
>> >
>> >
>> >

Re: Maven Assembly for MultiModule project

2008-03-07 Thread krishnan.1000

Hi Wayne,

I can not help it. I just joined a project to replace a guy who left the
project. So I am on an accelerated learning curve.

Thanks,

Karthik

Wayne Fay wrote:
> 
> It sounds like you're jumping in to complex builds with Maven2 without
> really understanding how things work at a basic level. As an example
> of this, you're running mvn install:install-file etc on what seems to
> be a Maven project -- so you really only need to type "mvn install".
> The same thing goes for your comment about "adding dependencies in all
> the pom.xml even if they have been specified in the parent." So I
> think you've skipped some important steps in your learning process.
> 
> I would go back to the beginning and work your way through Better
> Builds With Maven (free pdf book from devzuz.com) and Maven: The
> Definitive Guide (from sonatype.com). The books are organized such
> that you start out learning how Maven works internally (generally),
> and then they lead through some basic examples and finally take you
> through much more involved examples.
> 
> You should be able to do this in just 1 or 2 days, and I think you
> really need to invest this time now rather than attempting to hack
> your poms and assemblies just to make it work.
> 
> Wayne
> 
> On 3/7/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>>
>>  
>>
>>   
>>maven-compiler-plugin
>>2.1-20080129.223043-7
>>
>>  1.5
>>  1.5
>>
>>  
>>  
>> 
>>org.apache.maven.plugins
>>maven-surefire-plugin
>>2.4
>>
>>  
>>testng.xml
>>  
>>
>>  
>>  
>>maven-assembly-plugin
>>
>>  
>>jar-with-dependencies
>>  
>>  
>>
>>  true
>>  com.jbe.core.Foo
>>
>>  
>>
>>  
>>
>>  
>>
>> 
>>../pom.xml
>>0.1
>>foo-foo
>>foo
>>  
>>
>> I also find that I have to include foo-b in my foo's pom.xml in order to
>> compile even though, foo-a is dependent on foo-b and therefore must
>> compile
>> foo-b before foo-a.
>> 
>>  
>>  foo
>>  foo-a
>>  ${project.version}
>>  compile
>>
>> 
>>  foo
>>  foo-b
>>  ${project.version}
>>  compile
>> 
>> /dependencies>
>>
>> In addition, I have to add dependencies in all the pom.xml even if they
>> have
>> been specified in the parent pom.xml.
>>
>> Thanks,
>>
>> Karthik Krishnan
>>
>>
>>
>> krishnan.1000 wrote:
>> >
>> > Hi Wayne,
>> >
>> > I am sorry Wayne. I should have been more specific on the post. To
>> answer
>> > your first comment,  and I do not wish to sound rude, but if I knew
>> what I
>> > was doing wrong, I would not have posted in the first place.
>> >
>> > 2. I am trying to assemble a jar of module Foo and Bar . I wish that I
>> > create an executable jar with a defined main class and a classpath
>> added
>> > to MANIFEST.MF. So basically i want the to create foo.jar and bar.jar
>> > containing all the dependencies.
>> >
>> > 3. I find  that if i make the changes in Foo-A or FooB java classes,
>> and
>> > if i execute a mvn assembly:assembly, it does not build the FOO-A or
>> FOO-B
>> > in the .m2 repository before building Foo and Bar successfully again I
>> > have to get around that by doing the following
>> >
>> > mvn install:install-file
>> > -Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar
>> -DgroupId=project
>> > -DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar -DgeneratePOM=true,
>> the
>> > solution I found by doing a search on one of the posts.
>> >
>> > and again for foo-b. I would like to avoid that and just have mvn
>> > assembly:assembly do all this before creating foo.jar and bar.jar.
>> >
>> >
>> >
>> > Wayne Fay wrote:
>> >>
>> >> This list really works better if you post what you've done and then
>> >> tell us why its not working the way you wanted, or an error message
>> >> you got, etc. Looking at what you sent, I have no idea if it is
>> >> working how you expect or not.
>> >>
>> >> Sending your pom and assembly.xml file is probably not going to give
>> >> you the results you are hoping for. So, send a reply and be more clear
>> >> about what you've got vs what you want etc.
>> >>
>> >> Wayne
>> >>
>> >> On 3/6/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> I am a Maven newbie and I hope this is not a stupid question.  I am
>> >>> trying
>> >>> to create two Maven assembly jars for modules Foo and Bar. My project
>> --
>> >>> |
>> >>> |--- Bar
>> >>> |--- Foo
>> >>> |Foo-A
>> >>> |--- Foo-B
>> >>>
>> >>>
>> >>> This is my project structure. In this project, FOO-A is dependent on
>> >>> Foo-B
>> >>> and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly
>> >>> jars
>> >>> for both the for both Foo and Bar modules. Can you please help me?
>> >>>
>> >>> My project pom is as follows.
>> >>>

Re: Maven Assembly for MultiModule project

2008-03-07 Thread Wayne Fay
It sounds like you're jumping in to complex builds with Maven2 without
really understanding how things work at a basic level. As an example
of this, you're running mvn install:install-file etc on what seems to
be a Maven project -- so you really only need to type "mvn install".
The same thing goes for your comment about "adding dependencies in all
the pom.xml even if they have been specified in the parent." So I
think you've skipped some important steps in your learning process.

I would go back to the beginning and work your way through Better
Builds With Maven (free pdf book from devzuz.com) and Maven: The
Definitive Guide (from sonatype.com). The books are organized such
that you start out learning how Maven works internally (generally),
and then they lead through some basic examples and finally take you
through much more involved examples.

You should be able to do this in just 1 or 2 days, and I think you
really need to invest this time now rather than attempting to hack
your poms and assemblies just to make it work.

Wayne

On 3/7/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>
>  
>
>   
>maven-compiler-plugin
>2.1-20080129.223043-7
>
>  1.5
>  1.5
>
>  
>  
> 
>org.apache.maven.plugins
>maven-surefire-plugin
>2.4
>
>  
>testng.xml
>  
>
>  
>  
>maven-assembly-plugin
>
>  
>jar-with-dependencies
>  
>  
>
>  true
>  com.jbe.core.Foo
>
>  
>
>  
>
>  
>
> 
>../pom.xml
>0.1
>foo-foo
>foo
>  
>
> I also find that I have to include foo-b in my foo's pom.xml in order to
> compile even though, foo-a is dependent on foo-b and therefore must compile
> foo-b before foo-a.
> 
>  
>  foo
>  foo-a
>  ${project.version}
>  compile
>
> 
>  foo
>  foo-b
>  ${project.version}
>  compile
> 
> /dependencies>
>
> In addition, I have to add dependencies in all the pom.xml even if they have
> been specified in the parent pom.xml.
>
> Thanks,
>
> Karthik Krishnan
>
>
>
> krishnan.1000 wrote:
> >
> > Hi Wayne,
> >
> > I am sorry Wayne. I should have been more specific on the post. To answer
> > your first comment,  and I do not wish to sound rude, but if I knew what I
> > was doing wrong, I would not have posted in the first place.
> >
> > 2. I am trying to assemble a jar of module Foo and Bar . I wish that I
> > create an executable jar with a defined main class and a classpath added
> > to MANIFEST.MF. So basically i want the to create foo.jar and bar.jar
> > containing all the dependencies.
> >
> > 3. I find  that if i make the changes in Foo-A or FooB java classes, and
> > if i execute a mvn assembly:assembly, it does not build the FOO-A or FOO-B
> > in the .m2 repository before building Foo and Bar successfully again I
> > have to get around that by doing the following
> >
> > mvn install:install-file
> > -Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar -DgroupId=project
> > -DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar -DgeneratePOM=true, the
> > solution I found by doing a search on one of the posts.
> >
> > and again for foo-b. I would like to avoid that and just have mvn
> > assembly:assembly do all this before creating foo.jar and bar.jar.
> >
> >
> >
> > Wayne Fay wrote:
> >>
> >> This list really works better if you post what you've done and then
> >> tell us why its not working the way you wanted, or an error message
> >> you got, etc. Looking at what you sent, I have no idea if it is
> >> working how you expect or not.
> >>
> >> Sending your pom and assembly.xml file is probably not going to give
> >> you the results you are hoping for. So, send a reply and be more clear
> >> about what you've got vs what you want etc.
> >>
> >> Wayne
> >>
> >> On 3/6/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I am a Maven newbie and I hope this is not a stupid question.  I am
> >>> trying
> >>> to create two Maven assembly jars for modules Foo and Bar. My project --
> >>> |
> >>> |--- Bar
> >>> |--- Foo
> >>> |Foo-A
> >>> |--- Foo-B
> >>>
> >>>
> >>> This is my project structure. In this project, FOO-A is dependent on
> >>> Foo-B
> >>> and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly
> >>> jars
> >>> for both the for both Foo and Bar modules. Can you please help me?
> >>>
> >>> My project pom is as follows.
> >>>
> >>> 
> >>>Bar
> >>>Foo
> >>>Foo-A
> >>>Foo-B
> >>>  
> >>>
> >>>  
> >>>
> >>>  log4j
> >>>  log4j
> >>>  1.2.13
> >>>  compile
> >>>
> >>>
> >>>..
> >>>  
> >>>
> >>>  
> >>>
> >>>  
> >>>maven-assembly-plugin
> >>>
> >>>  
> >>>assembly.xml
> >>>  
> >>>  gnu
> >>>

Re: Maven Assembly for MultiModule project

2008-03-06 Thread krishnan.1000

 

   
maven-compiler-plugin
2.1-20080129.223043-7

  1.5
  1.5

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

  
testng.xml
  

  
  
maven-assembly-plugin

  
jar-with-dependencies
  
  

  true
  com.jbe.core.Foo

  

  

  


../pom.xml
0.1
foo-foo
foo
  

I also find that I have to include foo-b in my foo's pom.xml in order to
compile even though, foo-a is dependent on foo-b and therefore must compile
foo-b before foo-a.

 
  foo
  foo-a
  ${project.version}
  compile
 

  foo
  foo-b
  ${project.version}
  compile
 
/dependencies>

In addition, I have to add dependencies in all the pom.xml even if they have
been specified in the parent pom.xml. 

Thanks,

Karthik Krishnan



krishnan.1000 wrote:
> 
> Hi Wayne,
> 
> I am sorry Wayne. I should have been more specific on the post. To answer
> your first comment,  and I do not wish to sound rude, but if I knew what I
> was doing wrong, I would not have posted in the first place. 
> 
> 2. I am trying to assemble a jar of module Foo and Bar . I wish that I
> create an executable jar with a defined main class and a classpath added
> to MANIFEST.MF. So basically i want the to create foo.jar and bar.jar
> containing all the dependencies.
> 
> 3. I find  that if i make the changes in Foo-A or FooB java classes, and
> if i execute a mvn assembly:assembly, it does not build the FOO-A or FOO-B
> in the .m2 repository before building Foo and Bar successfully again I
> have to get around that by doing the following 
> 
> mvn install:install-file
> -Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar -DgroupId=project
> -DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar -DgeneratePOM=true, the
> solution I found by doing a search on one of the posts.
> 
> and again for foo-b. I would like to avoid that and just have mvn
> assembly:assembly do all this before creating foo.jar and bar.jar.
> 
> 
> 
> Wayne Fay wrote:
>> 
>> This list really works better if you post what you've done and then
>> tell us why its not working the way you wanted, or an error message
>> you got, etc. Looking at what you sent, I have no idea if it is
>> working how you expect or not.
>> 
>> Sending your pom and assembly.xml file is probably not going to give
>> you the results you are hoping for. So, send a reply and be more clear
>> about what you've got vs what you want etc.
>> 
>> Wayne
>> 
>> On 3/6/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi,
>>>
>>> I am a Maven newbie and I hope this is not a stupid question.  I am
>>> trying
>>> to create two Maven assembly jars for modules Foo and Bar. My project --
>>> |
>>> |--- Bar
>>> |--- Foo
>>> |Foo-A
>>> |--- Foo-B
>>>
>>>
>>> This is my project structure. In this project, FOO-A is dependent on
>>> Foo-B
>>> and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly
>>> jars
>>> for both the for both Foo and Bar modules. Can you please help me?
>>>
>>> My project pom is as follows.
>>>
>>> 
>>>Bar
>>>Foo
>>>Foo-A
>>>Foo-B
>>>  
>>>
>>>  
>>>
>>>  log4j
>>>  log4j
>>>  1.2.13
>>>  compile
>>>
>>>
>>>..
>>>  
>>>
>>>  
>>>
>>>  
>>>maven-assembly-plugin
>>>
>>>  
>>>assembly.xml
>>>  
>>>  gnu
>>>
>>>  
>>>  
>>>
>>>  
>>>
>>>  apache.snapshots
>>>  http://people.apache.org/repo/m2-snapshot-repository/
>>>
>>>  
>>>
>>> My assembly.xml
>>>
>>> 
>>>  jar-with-dependencies
>>>  
>>>jar
>>>  
>>>  false
>>>  
>>>
>>>  target/classes
>>>  /
>>>
>>>  
>>>  
>>>
>>>  /
>>>  false
>>>  runtime
>>>
>>>  
>>> 
>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Maven-Assembly-for-MultiModule-project-tp15885942s177p15885942.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]
>>>
>>>
>> 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Maven-Assembly-for-MultiModule-project-tp15885942s177p15890673.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 Assembly for MultiModule project

2008-03-06 Thread krishnan.1000

Hi Wayne,

I am sorry Wayne. I should have been more specific on the post. To answer
your first comment,  and I do not wish to sound rude, but if I knew what I
was doing wrong, I would not have posted in the first place. 

2. I am trying to assemble a jar of module Foo and Bar . I wish that I
create an executable jar with a defined main class and a classpath added to
MANIFEST.MF. So basically i want the to create foo.jar and bar.jar
containing all the dependencies.

3. I find  that if i make the changes in Foo-A or FooB java classes, and if
i execute a mvn assembly:assembly, it does not build the FOO-A or FOO-B in
the .m2 repository before building Foo and Bar successfully again I have to
get around that by doing the following 

mvn install:install-file
-Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar -DgroupId=project
-DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar -DgeneratePOM=true, the
solution I found by doing a search on one of the posts.

and again for foo-b. I would like to avoid that and just have mvn
assembly:assembly do all this before creating foo.jar and bar.jar.



Wayne Fay wrote:
> 
> This list really works better if you post what you've done and then
> tell us why its not working the way you wanted, or an error message
> you got, etc. Looking at what you sent, I have no idea if it is
> working how you expect or not.
> 
> Sending your pom and assembly.xml file is probably not going to give
> you the results you are hoping for. So, send a reply and be more clear
> about what you've got vs what you want etc.
> 
> Wayne
> 
> On 3/6/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> I am a Maven newbie and I hope this is not a stupid question.  I am
>> trying
>> to create two Maven assembly jars for modules Foo and Bar. My project --
>> |
>> |--- Bar
>> |--- Foo
>> |Foo-A
>> |--- Foo-B
>>
>>
>> This is my project structure. In this project, FOO-A is dependent on
>> Foo-B
>> and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly jars
>> for both the for both Foo and Bar modules. Can you please help me?
>>
>> My project pom is as follows.
>>
>> 
>>Bar
>>Foo
>>Foo-A
>>Foo-B
>>  
>>
>>  
>>
>>  log4j
>>  log4j
>>  1.2.13
>>  compile
>>
>>
>>..
>>  
>>
>>  
>>
>>  
>>maven-assembly-plugin
>>
>>  
>>assembly.xml
>>  
>>  gnu
>>
>>  
>>  
>>
>>  
>>
>>  apache.snapshots
>>  http://people.apache.org/repo/m2-snapshot-repository/
>>
>>  
>>
>> My assembly.xml
>>
>> 
>>  jar-with-dependencies
>>  
>>jar
>>  
>>  false
>>  
>>
>>  target/classes
>>  /
>>
>>  
>>  
>>
>>  /
>>  false
>>  runtime
>>
>>  
>> 
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Maven-Assembly-for-MultiModule-project-tp15885942s177p15885942.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]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Maven-Assembly-for-MultiModule-project-tp15885942s177p15890574.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 Assembly for MultiModule project

2008-03-06 Thread Wayne Fay
This list really works better if you post what you've done and then
tell us why its not working the way you wanted, or an error message
you got, etc. Looking at what you sent, I have no idea if it is
working how you expect or not.

Sending your pom and assembly.xml file is probably not going to give
you the results you are hoping for. So, send a reply and be more clear
about what you've got vs what you want etc.

Wayne

On 3/6/08, krishnan.1000 <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am a Maven newbie and I hope this is not a stupid question.  I am trying
> to create two Maven assembly jars for modules Foo and Bar. My project --
> |
> |--- Bar
> |--- Foo
> |Foo-A
> |--- Foo-B
>
>
> This is my project structure. In this project, FOO-A is dependent on Foo-B
> and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly jars
> for both the for both Foo and Bar modules. Can you please help me?
>
> My project pom is as follows.
>
> 
>Bar
>Foo
>Foo-A
>Foo-B
>  
>
>  
>
>  log4j
>  log4j
>  1.2.13
>  compile
>
>
>..
>  
>
>  
>
>  
>maven-assembly-plugin
>
>  
>assembly.xml
>  
>  gnu
>
>  
>  
>
>  
>
>  apache.snapshots
>  http://people.apache.org/repo/m2-snapshot-repository/
>
>  
>
> My assembly.xml
>
> 
>  jar-with-dependencies
>  
>jar
>  
>  false
>  
>
>  target/classes
>  /
>
>  
>  
>
>  /
>  false
>  runtime
>
>  
> 
>
>
> --
> View this message in context: 
> http://www.nabble.com/Maven-Assembly-for-MultiModule-project-tp15885942s177p15885942.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]
>
>

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