Re: Version range madness...

[Mark Derricutt]

Deployed to my Nexus repository, the metadata for the release is:


  smx3
  smx3.partyresource
  1.2.0
  
1.2.5

  1.2.0
  1.2.1
  1.2.2
  1.2.3
  1.2.4
  1.2.5

20081128050839
  


and the snapshot:


  smx3
  smx3.partyresource
  1.2.0-SNAPSHOT
  

  1.2.0-SNAPSHOT
  1.2.6-SNAPSHOT

20081130055646
  


Interesting - why is version 1.2.0, whilst theres a release of 1.2.5?
And the same with 1.2.0-SNAPSHOT as opposed to 1.2.6-SNAPSHOT.

In my settings.xml I have everything setup to mirror into nexus:

 

  Nexus
  Nexus Public Mirror
  http://XXX/nexus/content/groups/public
  *

  

with two server entries declaring my user/password to deploy.

 

  smx-releases
  admin
  XXX


  smx-snapshots
  admin
  XXX

  

On Sun, Nov 30, 2008 at 6:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
>> In my repository I have version 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4,
>> 1.2.5, and 1.2.6-SNAPSHOT deployed.  In my pom I have [1.2.0,)
>> declared as the version range.  This resolves to 1.2.0 whereas I
>> really want 1.2.6-SNAPSHOT to be resolved and used.  My understand is
>
> When you say "deployed", are you talking about actual remote
> deployment to a Maven repo manager? If so, what software are you using
> to host the repo? What does the content of the maven-metadata.xml file
> look like on the server?
>
> Also, did you declare that your repo hosts snapshots as well as
> releases in settings.xml?
>
> Wayne
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
"It is easier to optimize correct code than to correct optimized
code." -- Bill Harlan

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

Re: Version range madness...

[Wayne Fay]

> In my repository I have version 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4,
> 1.2.5, and 1.2.6-SNAPSHOT deployed.  In my pom I have [1.2.0,)
> declared as the version range.  This resolves to 1.2.0 whereas I
> really want 1.2.6-SNAPSHOT to be resolved and used.  My understand is

When you say "deployed", are you talking about actual remote
deployment to a Maven repo manager? If so, what software are you using
to host the repo? What does the content of the maven-metadata.xml file
look like on the server?

Also, did you declare that your repo hosts snapshots as well as
releases in settings.xml?

Wayne

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

Version range madness...

[Mark Derricutt]

'lo all,

A question on version ranges which is currently hurting my brain :)

In my repository I have version 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4,
1.2.5, and 1.2.6-SNAPSHOT deployed.  In my pom I have [1.2.0,)
declared as the version range.  This resolves to 1.2.0 whereas I
really want 1.2.6-SNAPSHOT to be resolved and used.  My understand is
that this means "any version greater than 1.2.0" but I really want
"the latest version greater than 1.2.0".  When I use [1.2.5,) maven
resolves 1.2.6-SNAPSHOT as I want, however this confuses me further as
I would have expected it to find 1.2.5.

Going from the other direction, I tried [,1.3.0) to say "anything up
to, but not including 1.3.0" which I expected would return
1.2.6-SNAPSHOT, but I still got 1.2.0.

Am I missing something simple here?  I'm using maven 2.0.9.

-- 
"It is easier to optimize correct code than to correct optimized
code." -- Bill Harlan

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

Re: MultiModule and DependencyManagement?

[Barrie Treloar]

On Sun, Nov 30, 2008 at 9:50 AM, Mohan K R <[EMAIL PROTECTED]> wrote:
> It appears that I'm missing something critical here, so please help me out.
> I have a standard
> multi-module project like this. (I'm using Maven 2.0.9, JDK5).
>
>  parent (P) -
>|- module A
>|- module B
>|- module C
[del]
> NOTE: I do use log4j in B, but it got transitively pulled in. So far so
> good.

WARNING!

It is BAD practice to use a dependency that you do not declare.

If you are using log4j in module B, make sure that you declare it.

You can use dependency:analyze to show you where you may need to fix things up.
It doesn't work very well on the test scopes because there is no
equivalent of "runtime" for test.

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

Re: MultiModule and DependencyManagement?

[Walid "jo" Gedeon]

Yes, I would tend to agree that this noted cell should be 'runtime'.
The case where there's a dependency to a class (B) that extends one from
another library (C) makes my code compile dependent on that library (C). I
think my project needs to keep track of the version of library C to avoid
surprises when changes happen.
But others may disagree :-)

On Sun, Nov 30, 2008 at 1:24 AM, Mohan K R <[EMAIL PROTECTED]> wrote:

> Thanks Walid. I think this is where my confusion is, the default scope is
> compile. And
> as per the matrix on the maven site it has an asterik describing the scope
> resolution.
> (for transitive dependencies)
>
> quote from docs: (
>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> )
>
> *(*) Note:* it is intended that this should be runtime scope instead, so
> that all compile dependencies must be explicitly listed - however, there is
> the case where the library you depend on extends a class from another
> library, forcing you to have available at compile time. For this reason,
> compile time dependencies remain as compile scope even when they are
> transitive.
>
> The above is the explanation for compile time dependency, as per above, it
> should not
> be runtime scope in C as you described or am I interpreting this wrong? It
> appears that
> if your explanation is right, then the doc should change that to runtime,
> at
> least that
> is what appears to be the behaviour in Maven 2.0.9.
>
>
> Thanks again
>
>
>
> On Sat, Nov 29, 2008 at 6:08 PM, Walid jo Gedeon <[EMAIL PROTECTED]>
> wrote:
>
> > Hello Mohan,
> >
> > In more technical jargon, log4j in your example is a compile time
> > dependency
> > of A, and only a runtime dependency of C, which means that if you want to
> > make log4j calls in C, you need to declare it as a compile time
> dependency
> > (default scope).
> >
> > HTH,
> > w
> >
> > On Sun, Nov 30, 2008 at 12:20 AM, Mohan K R <[EMAIL PROTECTED]> wrote:
> >
> > > It appears that I'm missing something critical here, so please help me
> > out.
> > > I have a standard
> > > multi-module project like this. (I'm using Maven 2.0.9, JDK5).
> > >
> > >  parent (P) -
> > >|- module A
> > >|- module B
> > >|- module C
> > >
> > >
> > > A,B,C all inherit from the parent P.
> > >
> > > Now in my parent POM (P): I have a dependencyManagement section in the
> > POM.
> > >  
> > >
> > >   
> > >   log4j
> > >   log4j
> > >   1.2.14
> > >   
> > >   <...  bunch of others ...>
> > >
> > >  
> > >
> > > Now in module A (I have a dependency on log4j), so only thing that I
> > > provide
> > > is (notice no version):
> > >
> > >
> > >   
> > >   log4j
> > >   log4j
> > >   
> > >   <...  bunch of others ...>
> > >
> > >
> > > Now in module B depends on module A so I have this in my dependency:
> > >
> > >   
> > >   ${project.groupId}
> > >   module_A 
> > >   ${project.version}
> > >   
> > >   <...  bunch of others ...*but no log4j*>
> > >
> > > NOTE: I do use log4j in B, but it got transitively pulled in. So far so
> > > good.
> > >
> > > Now Module C, depends on Module B. So what I have is:
> > >
> > >   
> > >   ${project.groupId}
> > >   module_B   
> > >   ${project.version}
> > >   
> > >   <...  bunch of others ...>
> > >
> > > Now, I do use some log4j calls (LogFactory), but for some reason log4j
> > does
> > > not
> > > get pulled in transitively??? I have to explicitly give a dependency on
> > > log4j *or*
> > > module_A to get it to compile??
> > >
> > > My first that was, all transitive dependencies on module_B should get
> > > pulled
> > > in which
> > > means module_A and in turn its transitive dependency log4j. But nothing
> > of
> > > this sort
> > > is happening? Any ideas? Is it the dependecyManagement section (which
> has
> > > the version)
> > > that is messing me up, since C does inherit from P?
> > >
> > > Thanks
> > > Mohan K
> > >
> >
>

Re: MultiModule and DependencyManagement?

[Mohan K R]

Thanks Walid. I think this is where my confusion is, the default scope is
compile. And
as per the matrix on the maven site it has an asterik describing the scope
resolution.
(for transitive dependencies)

quote from docs: (
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
)

*(*) Note:* it is intended that this should be runtime scope instead, so
that all compile dependencies must be explicitly listed - however, there is
the case where the library you depend on extends a class from another
library, forcing you to have available at compile time. For this reason,
compile time dependencies remain as compile scope even when they are
transitive.

The above is the explanation for compile time dependency, as per above, it
should not
be runtime scope in C as you described or am I interpreting this wrong? It
appears that
if your explanation is right, then the doc should change that to runtime, at
least that
is what appears to be the behaviour in Maven 2.0.9.


Thanks again



On Sat, Nov 29, 2008 at 6:08 PM, Walid jo Gedeon <[EMAIL PROTECTED]> wrote:

> Hello Mohan,
>
> In more technical jargon, log4j in your example is a compile time
> dependency
> of A, and only a runtime dependency of C, which means that if you want to
> make log4j calls in C, you need to declare it as a compile time dependency
> (default scope).
>
> HTH,
> w
>
> On Sun, Nov 30, 2008 at 12:20 AM, Mohan K R <[EMAIL PROTECTED]> wrote:
>
> > It appears that I'm missing something critical here, so please help me
> out.
> > I have a standard
> > multi-module project like this. (I'm using Maven 2.0.9, JDK5).
> >
> >  parent (P) -
> >|- module A
> >|- module B
> >|- module C
> >
> >
> > A,B,C all inherit from the parent P.
> >
> > Now in my parent POM (P): I have a dependencyManagement section in the
> POM.
> >  
> >
> >   
> >   log4j
> >   log4j
> >   1.2.14
> >   
> >   <...  bunch of others ...>
> >
> >  
> >
> > Now in module A (I have a dependency on log4j), so only thing that I
> > provide
> > is (notice no version):
> >
> >
> >   
> >   log4j
> >   log4j
> >   
> >   <...  bunch of others ...>
> >
> >
> > Now in module B depends on module A so I have this in my dependency:
> >
> >   
> >   ${project.groupId}
> >   module_A 
> >   ${project.version}
> >   
> >   <...  bunch of others ...*but no log4j*>
> >
> > NOTE: I do use log4j in B, but it got transitively pulled in. So far so
> > good.
> >
> > Now Module C, depends on Module B. So what I have is:
> >
> >   
> >   ${project.groupId}
> >   module_B   
> >   ${project.version}
> >   
> >   <...  bunch of others ...>
> >
> > Now, I do use some log4j calls (LogFactory), but for some reason log4j
> does
> > not
> > get pulled in transitively??? I have to explicitly give a dependency on
> > log4j *or*
> > module_A to get it to compile??
> >
> > My first that was, all transitive dependencies on module_B should get
> > pulled
> > in which
> > means module_A and in turn its transitive dependency log4j. But nothing
> of
> > this sort
> > is happening? Any ideas? Is it the dependecyManagement section (which has
> > the version)
> > that is messing me up, since C does inherit from P?
> >
> > Thanks
> > Mohan K
> >
>

Re: MultiModule and DependencyManagement?

[Mohan K R]

Thanks Stevo! Forgot to metion that it does work fine in eclipse (I'm using
m2eclipse plugin
but it fails when I compile it from the CLI). I will give the above project
a shot. Thanks again
Mohan

On Sat, Nov 29, 2008 at 6:05 PM, Stevo Slavić <[EMAIL PROTECTED]> wrote:

> Hello Mohan,
>
> Attached you can find an archive with eclipse maven multi-module project
> created as one you've described, so you can see transitive dependencies are
> working as expected. Your project is obviously somewhat different than what
> you described, and it is having effect on dependencies not being passed on.
> Check dependency scope and read 
> this,
> maybe it will help.
>
> Regards,
> Stevo.
>
>
> On Sun, Nov 30, 2008 at 12:20 AM, Mohan K R <[EMAIL PROTECTED]> wrote:
>
>> It appears that I'm missing something critical here, so please help me
>> out.
>> I have a standard
>> multi-module project like this. (I'm using Maven 2.0.9, JDK5).
>>
>>  parent (P) -
>>|- module A
>>|- module B
>>|- module C
>>
>>
>> A,B,C all inherit from the parent P.
>>
>> Now in my parent POM (P): I have a dependencyManagement section in the
>> POM.
>>  
>>
>>   
>>   log4j
>>   log4j
>>   1.2.14
>>   
>>   <...  bunch of others ...>
>>
>>  
>>
>> Now in module A (I have a dependency on log4j), so only thing that I
>> provide
>> is (notice no version):
>>
>>
>>   
>>   log4j
>>   log4j
>>   
>>   <...  bunch of others ...>
>>
>>
>> Now in module B depends on module A so I have this in my dependency:
>>
>>   
>>   ${project.groupId}
>>   module_A 
>>   ${project.version}
>>   
>>   <...  bunch of others ...*but no log4j*>
>>
>> NOTE: I do use log4j in B, but it got transitively pulled in. So far so
>> good.
>>
>> Now Module C, depends on Module B. So what I have is:
>>
>>   
>>   ${project.groupId}
>>   module_B   
>>   ${project.version}
>>   
>>   <...  bunch of others ...>
>>
>> Now, I do use some log4j calls (LogFactory), but for some reason log4j
>> does
>> not
>> get pulled in transitively??? I have to explicitly give a dependency on
>> log4j *or*
>> module_A to get it to compile??
>>
>> My first that was, all transitive dependencies on module_B should get
>> pulled
>> in which
>> means module_A and in turn its transitive dependency log4j. But nothing of
>> this sort
>> is happening? Any ideas? Is it the dependecyManagement section (which has
>> the version)
>> that is messing me up, since C does inherit from P?
>>
>> Thanks
>> Mohan K
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

Re: MultiModule and DependencyManagement?

[Walid "jo" Gedeon]

Hello Mohan,

In more technical jargon, log4j in your example is a compile time dependency
of A, and only a runtime dependency of C, which means that if you want to
make log4j calls in C, you need to declare it as a compile time dependency
(default scope).

HTH,
w

On Sun, Nov 30, 2008 at 12:20 AM, Mohan K R <[EMAIL PROTECTED]> wrote:

> It appears that I'm missing something critical here, so please help me out.
> I have a standard
> multi-module project like this. (I'm using Maven 2.0.9, JDK5).
>
>  parent (P) -
>|- module A
>|- module B
>|- module C
>
>
> A,B,C all inherit from the parent P.
>
> Now in my parent POM (P): I have a dependencyManagement section in the POM.
>  
>
>   
>   log4j
>   log4j
>   1.2.14
>   
>   <...  bunch of others ...>
>
>  
>
> Now in module A (I have a dependency on log4j), so only thing that I
> provide
> is (notice no version):
>
>
>   
>   log4j
>   log4j
>   
>   <...  bunch of others ...>
>
>
> Now in module B depends on module A so I have this in my dependency:
>
>   
>   ${project.groupId}
>   module_A 
>   ${project.version}
>   
>   <...  bunch of others ...*but no log4j*>
>
> NOTE: I do use log4j in B, but it got transitively pulled in. So far so
> good.
>
> Now Module C, depends on Module B. So what I have is:
>
>   
>   ${project.groupId}
>   module_B   
>   ${project.version}
>   
>   <...  bunch of others ...>
>
> Now, I do use some log4j calls (LogFactory), but for some reason log4j does
> not
> get pulled in transitively??? I have to explicitly give a dependency on
> log4j *or*
> module_A to get it to compile??
>
> My first that was, all transitive dependencies on module_B should get
> pulled
> in which
> means module_A and in turn its transitive dependency log4j. But nothing of
> this sort
> is happening? Any ideas? Is it the dependecyManagement section (which has
> the version)
> that is messing me up, since C does inherit from P?
>
> Thanks
> Mohan K
>

Re: Retrieve last artifact URL from remote repository

[Wendy Smoak]

On Sat, Nov 29, 2008 at 4:36 PM, Gerrit Brehmer <[EMAIL PROTECTED]> wrote:

> I want to do a remote deploy to a jboss server. For that I need the URL from
> the last deployment to the remote repository (timestamped snapshots e.g.,
> archiva server). The Url will be printed to the output console during/after
> successful archiva deployment (deploy:deploy). So can I retrieve this
> url/remote artifact name from a runtime property inside the pom? Or are
> there any other possibilities to get this information?

Probably more of a feature request for the Archiva list if that's what
you're using... I see there's a request in JIRA for browsing using
RELEASE and LATEST [1].

The metadata should be there in the repository, so you could read that
and construct the url.  Or, if you're using a plugin (Cargo?) to do
the deploy, it might be able to deal with snapshots.

[1] http://jira.codehaus.org/browse/MRM-805

-- 
Wendy

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

Retrieve last artifact URL from remote repository

[Gerrit Brehmer]

Hi,

I want to do a remote deploy to a jboss server. For that I need the URL from
the last deployment to the remote repository (timestamped snapshots e.g.,
archiva server). The Url will be printed to the output console during/after
successful archiva deployment (deploy:deploy). So can I retrieve this
url/remote artifact name from a runtime property inside the pom? Or are
there any other possibilities to get this information?

Thanks in advance

Bye, 
Gerrit




___ 
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: 
http://mail.yahoo.de


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

MultiModule and DependencyManagement?

[Mohan K R]

It appears that I'm missing something critical here, so please help me out.
I have a standard
multi-module project like this. (I'm using Maven 2.0.9, JDK5).

 parent (P) -
|- module A
|- module B
|- module C


A,B,C all inherit from the parent P.

Now in my parent POM (P): I have a dependencyManagement section in the POM.
 

   
   log4j
   log4j
   1.2.14
   
   <...  bunch of others ...>

 

Now in module A (I have a dependency on log4j), so only thing that I provide
is (notice no version):


   
   log4j
   log4j
   
   <...  bunch of others ...>


Now in module B depends on module A so I have this in my dependency:

   
   ${project.groupId}
   module_A 
   ${project.version}
   
   <...  bunch of others ...*but no log4j*>

NOTE: I do use log4j in B, but it got transitively pulled in. So far so
good.

Now Module C, depends on Module B. So what I have is:

   
   ${project.groupId}
   module_B   
   ${project.version}
   
   <...  bunch of others ...>

Now, I do use some log4j calls (LogFactory), but for some reason log4j does
not
get pulled in transitively??? I have to explicitly give a dependency on
log4j *or*
module_A to get it to compile??

My first that was, all transitive dependencies on module_B should get pulled
in which
means module_A and in turn its transitive dependency log4j. But nothing of
this sort
is happening? Any ideas? Is it the dependecyManagement section (which has
the version)
that is messing me up, since C does inherit from P?

Thanks
Mohan K

Re: How to place the project classpath into a ressource file?

[Brian Fox]

Heh... I Forgot about that

--Brian (mobile)


On Nov 29, 2008, at 2:06 PM, Stephan Niedermeier <[EMAIL PROTECTED] 
> wrote:



Hi,

got it. Thanks. For those interested in:

Use the "prefix" together with the "outputFilterFile" parameter of  
the build-classpath goal. Example:


  
  org.apache.maven.plugins
  maven-dependency-plugin
  
  true
  lib
  
  

Regards
Stephan

Stephan Niedermeier schrieb:

Hi Brian,

thanks for the hint, but it seems that the build-classpath goal  
calculates the full path to the jars (e.g. C:/project/lib/ 
myJar.jar). Is there a way to make this path relatively to, let's  
say "lib/" of the assembled folder?


Thanks a lot.

Regards
Stephan

Brian Fox schrieb:

You can use the maven-dependency-plugin:build-classpath goal

--Brian (mobile)


On Nov 29, 2008, at 11:28 AM, "Stephan Niedermeier" <[EMAIL PROTECTED] 
> wrote:



Hi,

I'm using Maven2 to build and assemble my project under Win XP.

The project contains a Java launcher. This launcher needs to know  
all

jars in the project. This will be done using a configuration file
(launcher.properties) and the property "app.classpath". The hard  
coded

entry for the property could look like this for example:

app.classpath=lib/commons-logging.jar;lib/commons-httpclient.jar

This works perfectly. But instead of hard coding and maintaining  
the
classpath in the configuration file as seen above, I would prefer  
using

some sort of Maven 2 Filter which calculates the classpath string
automatically and then places this string into my configuration  
file on

the predefined position. For example similar to this:

app.classpath=${someVarHoldingTheGeneratedClasspathString}

Im wondering whether there is a solution for this in Maven? I  
couldn't

find any hint in the Maven2 Filter docs, because there is no such
variable I could use. Maybe I have overseen something?

Any ideas how I can retrieve the classpath string and place it  
into my

configuration file?

PS: Putting the classpath into the META-INF using the   
tag is

not an option for me, because its not supported by the Launcher.

Thanks in advance.

Best regards
Stephan



--- 
--

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






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




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



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

Re: How to place the project classpath into a ressource file?

[Brian Fox]

I don't think so but it should be easy to patch

--Brian (mobile)


On Nov 29, 2008, at 1:39 PM, Stephan Niedermeier <[EMAIL PROTECTED] 
> wrote:



Hi Brian,

thanks for the hint, but it seems that the build-classpath goal  
calculates the full path to the jars (e.g. C:/project/lib/ 
myJar.jar). Is there a way to make this path relatively to, let's  
say "lib/" of the assembled folder?


Thanks a lot.

Regards
Stephan

Brian Fox schrieb:

You can use the maven-dependency-plugin:build-classpath goal

--Brian (mobile)


On Nov 29, 2008, at 11:28 AM, "Stephan Niedermeier" <[EMAIL PROTECTED] 
> wrote:



Hi,

I'm using Maven2 to build and assemble my project under Win XP.

The project contains a Java launcher. This launcher needs to know  
all

jars in the project. This will be done using a configuration file
(launcher.properties) and the property "app.classpath". The hard  
coded

entry for the property could look like this for example:

app.classpath=lib/commons-logging.jar;lib/commons-httpclient.jar

This works perfectly. But instead of hard coding and maintaining the
classpath in the configuration file as seen above, I would prefer  
using

some sort of Maven 2 Filter which calculates the classpath string
automatically and then places this string into my configuration  
file on

the predefined position. For example similar to this:

app.classpath=${someVarHoldingTheGeneratedClasspathString}

Im wondering whether there is a solution for this in Maven? I  
couldn't

find any hint in the Maven2 Filter docs, because there is no such
variable I could use. Maybe I have overseen something?

Any ideas how I can retrieve the classpath string and place it  
into my

configuration file?

PS: Putting the classpath into the META-INF using the   
tag is

not an option for me, because its not supported by the Launcher.

Thanks in advance.

Best regards
Stephan



--- 
--

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






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



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

Re: [Public service announcement] mirrors of Central and considerate repo use

[Paul Benedict]

I think Maven should download and configure itself with a list of
mirrors on first execution. Why leave this up to the users? I bet most
will likely not care to change.

Paul

On Sat, Nov 29, 2008 at 8:33 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 29, 2008 at 5:16 AM, Alex Athanasopoulos
> <[EMAIL PROTECTED]> wrote:
>
>> One of the most annoying problems I ran into with maven was when I setup a
>> central mirror containing my old local repository, deleted my local
>> repository, and then tried to rebuild it by doing a build.
>
> A local repo can't be used as a remote repo... while the directory
> structure looks the same, the metadata files are different.
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: How to place the project classpath into a ressource file?

[Stephan Niedermeier]

Hi,

got it. Thanks. For those interested in:

Use the "prefix" together with the "outputFilterFile" parameter of the 
build-classpath goal. Example:


   
   org.apache.maven.plugins
   maven-dependency-plugin
   
   true
   lib
   
   

Regards
Stephan

Stephan Niedermeier schrieb:

Hi Brian,

thanks for the hint, but it seems that the build-classpath goal 
calculates the full path to the jars (e.g. C:/project/lib/myJar.jar). 
Is there a way to make this path relatively to, let's say "lib/" of 
the assembled folder?


Thanks a lot.

Regards
Stephan

Brian Fox schrieb:

You can use the maven-dependency-plugin:build-classpath goal

--Brian (mobile)


On Nov 29, 2008, at 11:28 AM, "Stephan Niedermeier" 
<[EMAIL PROTECTED]> wrote:



Hi,

I'm using Maven2 to build and assemble my project under Win XP.

The project contains a Java launcher. This launcher needs to know all
jars in the project. This will be done using a configuration file
(launcher.properties) and the property "app.classpath". The hard coded
entry for the property could look like this for example:

app.classpath=lib/commons-logging.jar;lib/commons-httpclient.jar

This works perfectly. But instead of hard coding and maintaining the
classpath in the configuration file as seen above, I would prefer using
some sort of Maven 2 Filter which calculates the classpath string
automatically and then places this string into my configuration file on
the predefined position. For example similar to this:

app.classpath=${someVarHoldingTheGeneratedClasspathString}

Im wondering whether there is a solution for this in Maven? I couldn't
find any hint in the Maven2 Filter docs, because there is no such
variable I could use. Maybe I have overseen something?

Any ideas how I can retrieve the classpath string and place it into my
configuration file?

PS: Putting the classpath into the META-INF using the  
tag is

not an option for me, because its not supported by the Launcher.

Thanks in advance.

Best regards
Stephan



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






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




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

Re: How to place the project classpath into a ressource file?

[Stephan Niedermeier]

Hi Brian,

thanks for the hint, but it seems that the build-classpath goal 
calculates the full path to the jars (e.g. C:/project/lib/myJar.jar). Is 
there a way to make this path relatively to, let's say "lib/" of the 
assembled folder?


Thanks a lot.

Regards
Stephan

Brian Fox schrieb:

You can use the maven-dependency-plugin:build-classpath goal

--Brian (mobile)


On Nov 29, 2008, at 11:28 AM, "Stephan Niedermeier" 
<[EMAIL PROTECTED]> wrote:



Hi,

I'm using Maven2 to build and assemble my project under Win XP.

The project contains a Java launcher. This launcher needs to know all
jars in the project. This will be done using a configuration file
(launcher.properties) and the property "app.classpath". The hard coded
entry for the property could look like this for example:

app.classpath=lib/commons-logging.jar;lib/commons-httpclient.jar

This works perfectly. But instead of hard coding and maintaining the
classpath in the configuration file as seen above, I would prefer using
some sort of Maven 2 Filter which calculates the classpath string
automatically and then places this string into my configuration file on
the predefined position. For example similar to this:

app.classpath=${someVarHoldingTheGeneratedClasspathString}

Im wondering whether there is a solution for this in Maven? I couldn't
find any hint in the Maven2 Filter docs, because there is no such
variable I could use. Maybe I have overseen something?

Any ideas how I can retrieve the classpath string and place it into my
configuration file?

PS: Putting the classpath into the META-INF using the  tag is
not an option for me, because its not supported by the Launcher.

Thanks in advance.

Best regards
Stephan



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






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

Re: Third party jars

[Brian Fox]

You could save youself a lot of hassle with a repo manager. You  
shouldn't use local repos as remote repos because the metadata is  
different. Also with unmanaged repos, snapshot accumulation will  
become a problem.


--Brian (mobile)


On Nov 29, 2008, at 5:33 AM, "Alex Athanasopoulos" <[EMAIL PROTECTED] 
> wrote:



Why not put the jars in a repository?  A repository is perfect for
containing 3rd party jars, and one of maven's major benefits.  Once  
you do
that, you don't need to refer to the jars through a hardcoded path,  
but
simply by a portable artifact identifier.  You don't need any  
special tools
or repository managers, but you do need to setup your own remote  
repository

somehow.

I simply use mvn install:install-file, and then copy the generated  
files
from my local repository to a remote repository that I have created  
just for

3rd party libs.

I'm fairly new to maven, and this is one of the first things I had  
to do.

 The rest is just defining and managing repositories, which can be a
discussion of its own.  I'm not using any repository managers yet  
(learning

to live with maven is enough work for me right now).  My A-B-Cs of
repository management have been the following:

A)  At first I used only my local repository, which I shared with  
other
developers by putting it under version control in svn, just like I  
had my
3rd party libs before maven.   I used mvn -o most of the time, to  
avoid
accessing Maven's central repository.  I was a bit annoyed that I  
had to use

-o.  I tried to use the  configuration in settings.xml, but I
couldn't get it to work (one of my first frustrations with maven).   
mvn -o
worked reliably, but I had to remember to use it.  Whenever I needed  
a piece

of Maven that I didn't have, I used mvn without the -o flag, and once
everything worked, I added the new artifacts from my local  
repository to

svn.  I did not add my snapshots.

B)  I then figured out how to avoid the -o flag, by defining a  
mirror of the

central repository in my settings.xml.  The mirror was simply an
http-accessible location of the single svn-managed repository that I  
had.
 Whenever I needed to use a new piece of maven, I commented out the  
mirror
specifiction in my settings.xml, ran mvn so it could get new pieces  
from
repo1.maven.org, and then took the comment out of settings.xml.  The  
rest

was as in A.

C)  I now use two repositories:
1)  A repository of non-maven released artifacts.  Essentially this  
contains
3rd party libraries.  These are libraries that I've gotten directly  
from

their source, and which I've entered in the repository through
install:install-file.  I plan to also put my own released artifacts  
there.


2)  A central-mirror repository that has just the things that maven  
needs
(plugins and their dependencies).  This is the most difficult  
repository to
manage, and a source of problems, as I find maven's dependencies  
chaotic and

unstable.  This is why I've isolated them from my other artifacts.

D)  I plan to also use a snapshots repository that is automatically  
updated
with my daily build artifacts.  In fact, I may simply provide http  
access to

the daily build's local repository.
For now, I rebuild all of my artifacts locally.

Alex

On Fri, Nov 28, 2008 at 10:38 PM, <[EMAIL PROTECTED]>  
wrote:


> Hi,
>
> Is there any way to get the maven build process to include a set  
of jars
> when compiling/packaging that are not in the repository?  I have  
some
> vendor jars and I don't fancy packing them all up and placing them  
into

> the repository - I just want to point maven at a lib directory?
>
> Thanks,
>
>
> john
> ___
>
> This e-mail may contain information that is confidential,  
privileged or
> otherwise protected from disclosure. If you are not an intended  
recipient of
> this e-mail, do not duplicate or redistribute it by any means.  
Please delete
> it and any attachments and notify the sender that you have  
received it in
> error. Unless specifically indicated, this e-mail is not an offer  
to buy or
> sell or a solicitation to buy or sell any securities, investment  
products or

> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays. Any views or  
opinions
> presented are solely those of the author and do not necessarily  
represent

> those of Barclays. This e-mail is subject to terms available at the
> following link: www.barcap.com/emaildisclaimer. By messaging with  
Barclays
> you consent to the foregoing.  Barclays Capital is the investment  
banking
> division of Barclays Bank PLC, a company registered in England  
(number
> 1026167) with its registered office at 1 Churchill Place, London,  
E14 5HP.
>  This email may relate to or be sent from other members of the  
Barclays

> Group.
> ___
>
>  
--

Re: How to place the project classpath into a ressource file?

[Brian Fox]

You can use the maven-dependency-plugin:build-classpath goal

--Brian (mobile)


On Nov 29, 2008, at 11:28 AM, "Stephan Niedermeier" <[EMAIL PROTECTED] 
> wrote:



Hi,

I'm using Maven2 to build and assemble my project under Win XP.

The project contains a Java launcher. This launcher needs to know all
jars in the project. This will be done using a configuration file
(launcher.properties) and the property "app.classpath". The hard coded
entry for the property could look like this for example:

app.classpath=lib/commons-logging.jar;lib/commons-httpclient.jar

This works perfectly. But instead of hard coding and maintaining the
classpath in the configuration file as seen above, I would prefer  
using

some sort of Maven 2 Filter which calculates the classpath string
automatically and then places this string into my configuration file  
on

the predefined position. For example similar to this:

app.classpath=${someVarHoldingTheGeneratedClasspathString}

Im wondering whether there is a solution for this in Maven? I couldn't
find any hint in the Maven2 Filter docs, because there is no such
variable I could use. Maybe I have overseen something?

Any ideas how I can retrieve the classpath string and place it into my
configuration file?

PS: Putting the classpath into the META-INF using the   
tag is

not an option for me, because its not supported by the Launcher.

Thanks in advance.

Best regards
Stephan



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

How to place the project classpath into a ressource file?

[Stephan Niedermeier]

Hi,

I'm using Maven2 to build and assemble my project under Win XP.

The project contains a Java launcher. This launcher needs to know all 
jars in the project. This will be done using a configuration file 
(launcher.properties) and the property "app.classpath". The hard coded 
entry for the property could look like this for example:


app.classpath=lib/commons-logging.jar;lib/commons-httpclient.jar

This works perfectly. But instead of hard coding and maintaining the 
classpath in the configuration file as seen above, I would prefer using 
some sort of Maven 2 Filter which calculates the classpath string 
automatically and then places this string into my configuration file on 
the predefined position. For example similar to this:


app.classpath=${someVarHoldingTheGeneratedClasspathString}

Im wondering whether there is a solution for this in Maven? I couldn't 
find any hint in the Maven2 Filter docs, because there is no such 
variable I could use. Maybe I have overseen something?


Any ideas how I can retrieve the classpath string and place it into my 
configuration file?


PS: Putting the classpath into the META-INF using the  tag is 
not an option for me, because its not supported by the Launcher.


Thanks in advance.

Best regards
Stephan



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

Re: [Public service announcement] mirrors of Central and considerate repo use

[Wendy Smoak]

On Sat, Nov 29, 2008 at 5:16 AM, Alex Athanasopoulos
<[EMAIL PROTECTED]> wrote:

> One of the most annoying problems I ran into with maven was when I setup a
> central mirror containing my old local repository, deleted my local
> repository, and then tried to rebuild it by doing a build.

A local repo can't be used as a remote repo... while the directory
structure looks the same, the metadata files are different.

-- 
Wendy

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

Re: [Public service announcement] mirrors of Central and considerate repo use

[Wendy Smoak]

On Sat, Nov 29, 2008 at 6:48 AM, Torsten Werner
<[EMAIL PROTECTED]> wrote:

> me too! ;-) And I like to have a minimal zip file: just one version of
> every core plugin and one version every direct or indirect dependency
> - not 4 versions of commons-collections, 4 versions of
> commons-logging, 3 versions of maven-plugin-plugin, etc.

You could get pretty close with the Assembly plugin's ability to build
a repository [1].  However, the problem I always run into is that,
like all Maven builds, it chooses *one* version of each dependency.
That means if you try to create a download with all the core plugins,
and the site plugin wants foo-1.0.jar, but the resources plugin wants
foo-2.0.jar, the resulting repository won't be complete.  You'd have
to build a repository for each plugin, and merge them all together.

[1] 
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-repositories.html

-- 
Wendy

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

Re: A jar replace another jar

[Baptiste MATHUS]

Well, I'm not sure I got all your points, but it seems like you're using
provided scope just to break transitive dependency, is it? If so, then you
might want to begin by using true instead.

If your p0 jar is not to be used directly, why not consider weaving aspects
during the compile phase and publish the resulting jar instead in your
corporate repository? I never used AspectJ but I've heard some times that
one strategy was in fact no to use the javaagent but instead do it while
compiling.

If you cannot consider the compile-time weaving, but that p0 is never to be
used directly as a dependency.  Then one thing to prevent that is to use the
enforcer plugin to forbid this particular dependency.

There might other solutions, depending on the precisions you give.

Cheers.
PS : global dependency exclusion is not possible yet; see
http://jira.codehaus.org/browse/MNG-1977. I seem to remember there was a
plugin that'd let you do it but I'm not sure at all.

2008/11/29 Rice Yeh <[EMAIL PROTECTED]>

> Hi,
>  I have a project called p1 using aspectj to instrument another jar called
> p0.jar to get its artifact p1.jar. Then p1.jar is aimed to replace p0
> wherever p0 is used. Therefore, in p1's pom, I set the scope of the
> dependence on p0 to be 'provided' and include all dependencies from p0.
> However, for a project, say p2, depending on p1, it is still possbile to
> have p0 included through other dependencies that depend on p0. Although I
> can exclude p0 in those dependencies in p2's pom, it seems not that good in
> the solution.  Is there a better way to solve this problem?
>
> Regards,
> Rice
>



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

Re: [Public service announcement] mirrors of Central and considerate repo use

[Torsten Werner]

Hi,

On Sat, Nov 29, 2008 at 1:16 PM, Alex Athanasopoulos
<[EMAIL PROTECTED]> wrote:
> I wish that I could download a zip file containing the subset of central
> containing maven's core plugins and their dependencies.

me too! ;-) And I like to have a minimal zip file: just one version of
every core plugin and one version every direct or indirect dependency
- not 4 versions of commons-collections, 4 versions of
commons-logging, 3 versions of maven-plugin-plugin, etc.

Cheers,
Torsten

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

Re: [Public service announcement] mirrors of Central and considerate repo use

[Alex Athanasopoulos]

This touches on my pet peeve about maven.

I wish that I could download a zip file containing the subset of central
containing maven's core plugins and their dependencies.  I would then gladly
use it as my central mirror and work productively on my projects without
having to worry about central.

I also wish that Maven did not access a central online repository by
default, so I wouldn't have to go through the extra effort of preventing it
from doing so.  When Maven is installed "out of the box", it could be
configured to use its own self-contained repository that came with the
installation.  If I want non-core plugins or other things, then I could tell
maven to use an online repository.

In other words, I want an integration-tested self-contained maven release.
 Is that a lot to ask for from a dependency management tool?  I don't have
that now, so I have to do my own version managemnet of all maven plugins
that I use.  When I try to use a plugin or a plugin feature that I haven't
used before, I have to go through a sometimes painful process of figuring
out which is the version of the plugin that works and is consistent with all
my existing projects and plugins.  I've more than once used a plugin version
mentioned in the documentation,  only to find out that it's buggy or
obsolete and I need to use a newer version (or sometimes even a completely
different groupId/artifactId).

Can maven, the tool, be separated from central, the grand repository of java
libraries?  I don't want central.  If I want library X for my projects, I
can go to library X's website, download X, and add it to my repository.  If
library X wants to be maven-friendly, it can include a script that lets me
add all its jar files to my repository easily, so I don't have to add them
one by one manually.

Wouldn't this reduce traffic to maven central?

But maven doesn't come in a box.  Instead, it lets its plugins download
whatever dependencies they want from central.  It seems that it even gives
them the freedom to specify a range of versions, or any random version they
find, so that what a build does is unpredictable and dependent on the
vagaries of a moving target central repository.  It's amazing that it works
most of the time, but it fails too often for me.

One of the most annoying problems I ran into with maven was when I setup a
central mirror containing my old local repository, deleted my local
repository, and then tried to rebuild it by doing a build.  mvn went on to
happily copy things from my central mirror, until it couldn't resolve a
dependency.  It has something to do with a "RELEASE" version of a plugin not
being found.  I have aparently gotten a central artifact at some point in
time that has an integration problem with other artifacts and ends up using
an artifact version that it doesn't explicitly ask for.  I believe it's
related to the site plugin, which I have since stopped trying to use.  In
the end, I went back to copying my central mirror to my local repository
(something easily done with svn, which I use as my repository manager).

-Alex

On Tue, Nov 25, 2008 at 5:27 PM, Brian E. Fox <[EMAIL PROTECTED]>wrote:

> The central repo has been undergoing significant load lately, most
> likely the result of people crawling and attempting to download all 70GB
> of it. I'd like to point out the availability of additional mirrors that
> you can use to increase your download performance and reduce the load on
> central. These mirrors are updated daily right after central pulls in
> all the new artifacts, so they are as fresh as central. Find the list of
> mirrors here[1].
>
>
>
> Also, for those of you with multiple developers in a single location not
> using a repo manager, what are you waiting for? There are plenty to
> choose from and numerous reasons to do so, particularly the ability to
> isolate yourself from transitive network outages or slowdowns. You can
> read more about why and the existing repo managers at [2],[3] and a
> comparison grid here at [4]
>
>
>
> Also, if you are using a repo manager, make sure to correctly configure
> it to not make requests to public repositories for your internal
> artifacts. Otherwise you are making a ton of requests for things that
> will never be found, increasing the bandwidth usage on your side and
> ours. Also it gives away potentially sensitive information as someone
> could scrape the logs and figure out what you're up to internally based
> on these requests. Nexus lets you configure routing rules so you could
> exclude com.yourcompany.* from central. Archiva has similar
> functionality, I'm not sure about Artifactory.
>
>
>
> Please be a polite repository user. These repos and mirrors are provided
> free of charge but there is a real cost behind providing this bandwidth.
> Scraping the entire repository starves other users and increases the
> cost of providing these repositories to the community. If the mirrors
> start getting abused then we may find less geographical redundancy 

Re: version for submodules

[Stephen Connolly]

FYI, versions-maven-plugin is out of the sandbox and has 1.0-alpha-1  
pushed to central


Sent from my iPod

On 29 Nov 2008, at 04:49, "Wendy Smoak" <[EMAIL PROTECTED]> wrote:

On Fri, Nov 28, 2008 at 9:43 PM, Erwin Mueller <[EMAIL PROTECTED] 
> wrote:


I don't like to update the version for the parent in each module's  
pom

file, is there a solution?


Barrie mentioned the release plugin and there is also a Versions
plugin at Codehaus Mojo (possibly still in the sandbox though).

--
Wendy

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



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

Re: Third party jars

[Alex Athanasopoulos]

Why not put the jars in a repository?  A repository is perfect for
containing 3rd party jars, and one of maven's major benefits.  Once you do
that, you don't need to refer to the jars through a hardcoded path, but
simply by a portable artifact identifier.  You don't need any special tools
or repository managers, but you do need to setup your own remote repository
somehow.

I simply use mvn install:install-file, and then copy the generated files
from my local repository to a remote repository that I have created just for
3rd party libs.

I'm fairly new to maven, and this is one of the first things I had to do.
 The rest is just defining and managing repositories, which can be a
discussion of its own.  I'm not using any repository managers yet (learning
to live with maven is enough work for me right now).  My A-B-Cs of
repository management have been the following:

A)  At first I used only my local repository, which I shared with other
developers by putting it under version control in svn, just like I had my
3rd party libs before maven.   I used mvn -o most of the time, to avoid
accessing Maven's central repository.  I was a bit annoyed that I had to use
-o.  I tried to use the  configuration in settings.xml, but I
couldn't get it to work (one of my first frustrations with maven).  mvn -o
worked reliably, but I had to remember to use it.  Whenever I needed a piece
of Maven that I didn't have, I used mvn without the -o flag, and once
everything worked, I added the new artifacts from my local repository to
svn.  I did not add my snapshots.

B)  I then figured out how to avoid the -o flag, by defining a mirror of the
central repository in my settings.xml.  The mirror was simply an
http-accessible location of the single svn-managed repository that I had.
 Whenever I needed to use a new piece of maven, I commented out the mirror
specifiction in my settings.xml, ran mvn so it could get new pieces from
repo1.maven.org, and then took the comment out of settings.xml.  The rest
was as in A.

C)  I now use two repositories:
1)  A repository of non-maven released artifacts.  Essentially this contains
3rd party libraries.  These are libraries that I've gotten directly from
their source, and which I've entered in the repository through
install:install-file.  I plan to also put my own released artifacts there.

2)  A central-mirror repository that has just the things that maven needs
(plugins and their dependencies).  This is the most difficult repository to
manage, and a source of problems, as I find maven's dependencies chaotic and
unstable.  This is why I've isolated them from my other artifacts.

D)  I plan to also use a snapshots repository that is automatically updated
with my daily build artifacts.  In fact, I may simply provide http access to
the daily build's local repository.
For now, I rebuild all of my artifacts locally.

Alex

On Fri, Nov 28, 2008 at 10:38 PM, <[EMAIL PROTECTED]> wrote:

> Hi,
>
> Is there any way to get the maven build process to include a set of jars
> when compiling/packaging that are not in the repository?  I have some
> vendor jars and I don't fancy packing them all up and placing them into
> the repository - I just want to point maven at a lib directory?
>
> Thanks,
>
>
> john
> ___
>
> This e-mail may contain information that is confidential, privileged or
> otherwise protected from disclosure. If you are not an intended recipient of
> this e-mail, do not duplicate or redistribute it by any means. Please delete
> it and any attachments and notify the sender that you have received it in
> error. Unless specifically indicated, this e-mail is not an offer to buy or
> sell or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays. Any views or opinions
> presented are solely those of the author and do not necessarily represent
> those of Barclays. This e-mail is subject to terms available at the
> following link: www.barcap.com/emaildisclaimer. By messaging with Barclays
> you consent to the foregoing.  Barclays Capital is the investment banking
> division of Barclays Bank PLC, a company registered in England (number
> 1026167) with its registered office at 1 Churchill Place, London, E14 5HP.
>  This email may relate to or be sent from other members of the Barclays
> Group.
> ___
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>