mail-lists.xml patch

2004-03-03 Thread Tim Pizey
Hi, 

A patch for maven-plugins/xdoc/src/plugin-resources/templates/mail-lsits.xml

-#if ($link.startsWith("http"))
+#if ($link.trim().startsWith("http"))

looks like this is a hack to overcomne the fact that leading spaces 
are being included in the variable. 

yours
Tim Pizey
Index: mail-lists.xml
===
RCS file: /home/cvspublic/maven-plugins/xdoc/src/plugin-resources/templates/mail-lists.xml,v
retrieving revision 1.3
diff -u -r1.3 mail-lists.xml
--- mail-lists.xml	2 Feb 2004 04:40:25 -	1.3
+++ mail-lists.xml	3 Mar 2004 20:40:30 -
@@ -3,7 +3,7 @@
 #macro (displayLink $label $link)
 
   #if ($link && $link.length() != 0)
-#if ($link.startsWith("http"))
+#if ($link.trim().startsWith("http"))
   $label
 #else
   mailto:$link";>$label

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

Re: Problem with assert in jellydoc

2004-03-03 Thread Tim Pizey
Hi, 

I hope that reporting these problems is helpful. 

I have upgraded maven to 1.0-rc1 and the jellydoc report 
still cannot handle assert and is still reporting itself as javadoc. 

The checkstyle report has stopped working, 
saying that I have content in my prolog. 

maven.log reports many problems with parsing html as ant commands
The actual output does not go to maven.log and is 
so verbose I cannot capture it in my xterm. 

Astonishingly the word 'PanEris' is split into 'PanEr is' within the 
Organisation. 
Much other spurious white space is introduced. 

Even if no time zone is present a TZ Offset / Time  is printed. 
Contributors are mentioned even if there aren't any. 

ampersand entities within urls are not respected. 
The subscribe/unsubscribe links are being rendered as 
mailtos even though they start with http://
(again a whitespace issue I believe)

I cannot get CVS HEAD to work locally. 

I would wish to see the distributions directory below docs, 
well to be honest I would like to see everything in docs moved up to 
target. Then I would set that as my Document-Root. 

Whilst in review mode I would lose the collapsed and expanded images. 

The above problems can be seen at 
http://spindent.paneris.net/

yours
tim pizey


On Wednesday 03 March 2004 3:06 pm, Tim Pizey wrote:
> Hi,
>
> I am running out of cvs on my local machine
> but using 1.0-beta-9 on the production machine.
> Both systems are running j2sdk1.4.2
>
> maven dist works on both
>
> On the production machine maven site fails with
>
> [javadoc]
> /usr/local/packages/dist/SPIndent/build/org/paneris/spindent/set/quasi/Toke
>nSet.java:128: warning: as of release 1.4, assert is a keyword, and may not
> be used as an identifier
> [javadoc] assert !(one instanceof ComplexTokenSet) || !(two
> instanceof ComplexTokenSet);
> [javadoc] ^
> [javadoc]
> /usr/local/packages/dist/SPIndent/build/org/paneris/spindent/set/quasi/Toke
>nSet.java:128: not a statement
> [javadoc] assert !(one instanceof ComplexTokenSet) || !(two
> instanceof ComplexTokenSet);
> [javadoc] ^
> [javadoc]
> /usr/local/packages/dist/SPIndent/build/org/paneris/spindent/set/quasi/Toke
>nSet.java:128: ';' expected
> [javadoc] assert !(one instanceof ComplexTokenSet) || !(two
> instanceof ComplexTokenSet);
> [javadoc]^
>
> BUILD FAILED
> null:37:50:  null:70:84:  Warning: Could not find
> file /usr/local/packages/dist/SPIndent/target/taglib.xml to copy.
> Total time: 1 minutes 56 seconds
>
> I have the following in project.properties
> maven.compile.deprecation = on
> maven.compile.optimize = off
> maven.compile.debug = on
> maven.compile.source = 1.4
> maven.compile.target = 1.4
> maven.javadoc.source = 1.4
> maven.test.source = 1.4
> maven.javadoc.customtags=todo
> todo.name=todo
> todo.description="To Do:"
>
>
> Any clues?
>
> cheers
> timp
>
>
>
>
> -
> 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]



running Java applications

2004-03-03 Thread Volkmann, Mark
The following goal works well for running a Java application from Maven.
I'm surprised there is nothing like this in the java plugin.  Do I really
have to write this myself for every project that needs it or is there
already something supplied with Maven to do this?

  



  
  

  

  


-
A.G. Edwards & Sons' outgoing and incoming e-mails are electronically
archived and subject to review and/or disclosure to someone other 
than the recipient.

-



[jar:deploy] Problem on Windows

2004-03-03 Thread Jeffrey, Rashid
Hi

Our team's remote repository lives on a Windows machine. By issuing a
 goal I get this error which seems to be expecting a target Unix
machine:

Execute failed: java.io.IOException: CreateProcess: ssh -l rashid
//ost-java-dev/javadch
ome "mkdir -p //ost-java-dev/javadchome/respository/com.sky.utils/jars"
error=2

Although this goal doesn't work for me:
invokes 

...these goals work fine:
invokes 
invokes 
invokes 

NOTE:  vs. 

As a work around, I have written a postGoal for  that calls
, which successfully uploads the jar to the remote
repository, but it's not a satisfactory long term solution.

How can I deploy jars to our remote repository in the same way that we do
for ears/ejbs/ears?

Thanks, Rashid.



---
Information in this email may be privileged, confidential and is 
intended exclusively for the addressee.  The views expressed may
not be official policy, but the personal views of the originator.
If you have received it in error, please notify the sender by return
e-mail and delete it from your system.  You should not reproduce, 
distribute, store, retransmit, use or disclose its contents to anyone.
 
Please note we reserve the right to monitor all e-mail
communication through our internal and external networks.
---



RE: Download of SNAPSHOT-Plugins

2004-03-03 Thread Jean-Marc Lavoie
This make sense as you can be working on a branch to release a maintenance version.

Let say your team released gizmosoft 1.0, and you work on new and improved version 1.1 
so you have 1.1-rc1-SNAPSHOT (or whatever you like: b1, b2 instead of rc1). Then you 
must apply a fix to 1.0, you branch to produce the new, improved and working 1.0.1 
which will have a bug fix. You call this snapshot 1.0.1-SNAPSHOT (Let say that for a 
medium fix you will skip the RC1 step). This way you have 2 SNAPSHOT at the same time, 
and your certain of which one you get. Adding RC1 should prevent you from eventually 
getting the RC2 snapshot as it may introduce potential big changes compared to RC1, 
when you are ready you simply change it to RC2. If you build sources that are between 
releases you can expect some weird things, those are development snapshots.

I'm not on the maven team, but this numbering make sense to me.

How else would you suggest this should be done?


-Original Message-
From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 12:29 PM
To: Maven Users List
Subject: AW: Download of SNAPSHOT-Plugins


Hi Martin,

for me the SNAPSHOT idea of Maven seems to be not completely mature. E.g. if
you look at the project.xml of Maven itself (e.g. here:
http://cvs.apache.org/viewcvs.cgi/maven/project.xml?rev=1.317.4.12&view=mark
up) you'll find that their current version is named 1.0-rc2-SNAPSHOT. When
setting up our projects I used the Maven project as a kind of copy-paste
template.

Cheers,
Joern

> -Ursprüngliche Nachricht-
> Von: Martin Lambert [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 3. März 2004 13:06
> An: Maven Users List
> Betreff: RE: Download of SNAPSHOT-Plugins
> 
> 
> Hi Joern,
> 
> Glad I helped solve that problem. 
> 
> I am under the impression though that 'SNAPSHOT' in Maven is 
> the latest development version. Fixed version numbers I 
> believe are meant to represent stable versions of code. You 
> appear to be muddying the waters with your versioning 
> numbering system.
> 
> Cheers,
> 
> Martin.
> 
> -Original Message-
> From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
> Sent: 03 March 2004 11:52
> To: Maven Users List
> Subject: AW: Download of SNAPSHOT-Plugins
> 
> 
> Hi Martin,
> 
> '1.2-SNAPSHOT' means that it is the version 1.2 of the plugin 
> that is still
> in development and changes until version 1.2 is released. And 
> I wanted to
> use 
> 
> maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
> -Dversion=1.2-SNAPSHOT 
> 
> to download the latest version of the nightly build of that 
> maven plugin.
> 
> But anyway, you helped me out with another problem I had with 
> the versioning
> of Maven plugins that are used to build an artifact. Until now I had a
> proplem with building older versions of our project (e.g. for 
> bug-fixing
> branches). The source-code, project.xml etc. was revisioned 
> in CVS, however
> the versions of the plugins that were used to build the project are
> mentioned nowhere. I.e. if you install a newer version of a 
> plugin on your
> computer it might screw up the original build. However, if 
> you explicitely
> write down in the project.xml the dependencies to the plugins 
> you are using,
> you can reproduce your revisioned project.
> 
> Joern
> 
> > -Ursprüngliche Nachricht-
> > Von: Martin Lambert [mailto:[EMAIL PROTECTED]
> > Gesendet: Mittwoch, 3. März 2004 12:03
> > An: Maven Users List
> > Betreff: RE: Download of SNAPSHOT-Plugins
> > 
> > 
> > Hi,
> > 
> > I'm not sure what you're on about with 1.2-SNAPSHOT, my 
> > understanding is you either have 'SNAPSHOT' which will always 
> > pull down the latest version or a fixed version number which 
> > I guess Maven would see '1.2-SNAPSHOT' as.
> > 
> > Try this in the project.xml of a project that needs to use 
> the plugin:
> > 
> > 
> >  
> > my-plugins
> > my-plugin
> > SNAPSHOT
> >   PLUGIN
> >  
> > 
> > Hope this helps,
> > 
> > Martin.
> > 
> > -Original Message-
> > From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
> > Sent: 03 March 2004 10:56
> > To: Maven Users List
> > Subject: Download of SNAPSHOT-Plugins
> > 
> > 
> > Hi,
> > 
> > by reading the Jelly script of the Plugin Plugin I figured 
> > out that if you
> > want to downlaod the current version of a plugin like this:
> > 
> > maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
> > -Dversion=1.2-SNAPSHOT 
> > 
> > and you already have a 1.2-SNAPSHOT version on your disk, it 
> > doesn't update
> > it with a newer version. As this is oky for non SNAPSHOT 
> > versions, I would
> > expect to SNAPSHOT behaviour for SNAPSHOT versions.
> > Is there any other elegant way to download and install the 
> > latest version of
> > a plugin with a SNAPSHOT version?
> > 
> > Joern
> > 
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional comman

RE: Download of SNAPSHOT-Plugins

2004-03-03 Thread Jörg Schaible
Martin Lambert wrote on Wednesday, March 03, 2004 1:06 PM:

> Hi Joern,
> 
> Glad I helped solve that problem.
> 
> I am under the impression though that 'SNAPSHOT' in Maven is
> the latest development version. Fixed version numbers I
> believe are meant to represent stable versions of code. You
> appear to be muddying the waters with your versioning numbering
> system. 

You have both. Think of something like Tomcat. 

Regards,
Jörg

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



AW: Download of SNAPSHOT-Plugins

2004-03-03 Thread Jörn Gebhardt
Hi Martin,

for me the SNAPSHOT idea of Maven seems to be not completely mature. E.g. if
you look at the project.xml of Maven itself (e.g. here:
http://cvs.apache.org/viewcvs.cgi/maven/project.xml?rev=1.317.4.12&view=mark
up) you'll find that their current version is named 1.0-rc2-SNAPSHOT. When
setting up our projects I used the Maven project as a kind of copy-paste
template.

Cheers,
Joern

> -Ursprüngliche Nachricht-
> Von: Martin Lambert [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 3. März 2004 13:06
> An: Maven Users List
> Betreff: RE: Download of SNAPSHOT-Plugins
> 
> 
> Hi Joern,
> 
> Glad I helped solve that problem. 
> 
> I am under the impression though that 'SNAPSHOT' in Maven is 
> the latest development version. Fixed version numbers I 
> believe are meant to represent stable versions of code. You 
> appear to be muddying the waters with your versioning 
> numbering system.
> 
> Cheers,
> 
> Martin.
> 
> -Original Message-
> From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
> Sent: 03 March 2004 11:52
> To: Maven Users List
> Subject: AW: Download of SNAPSHOT-Plugins
> 
> 
> Hi Martin,
> 
> '1.2-SNAPSHOT' means that it is the version 1.2 of the plugin 
> that is still
> in development and changes until version 1.2 is released. And 
> I wanted to
> use 
> 
> maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
> -Dversion=1.2-SNAPSHOT 
> 
> to download the latest version of the nightly build of that 
> maven plugin.
> 
> But anyway, you helped me out with another problem I had with 
> the versioning
> of Maven plugins that are used to build an artifact. Until now I had a
> proplem with building older versions of our project (e.g. for 
> bug-fixing
> branches). The source-code, project.xml etc. was revisioned 
> in CVS, however
> the versions of the plugins that were used to build the project are
> mentioned nowhere. I.e. if you install a newer version of a 
> plugin on your
> computer it might screw up the original build. However, if 
> you explicitely
> write down in the project.xml the dependencies to the plugins 
> you are using,
> you can reproduce your revisioned project.
> 
> Joern
> 
> > -Ursprüngliche Nachricht-
> > Von: Martin Lambert [mailto:[EMAIL PROTECTED]
> > Gesendet: Mittwoch, 3. März 2004 12:03
> > An: Maven Users List
> > Betreff: RE: Download of SNAPSHOT-Plugins
> > 
> > 
> > Hi,
> > 
> > I'm not sure what you're on about with 1.2-SNAPSHOT, my 
> > understanding is you either have 'SNAPSHOT' which will always 
> > pull down the latest version or a fixed version number which 
> > I guess Maven would see '1.2-SNAPSHOT' as.
> > 
> > Try this in the project.xml of a project that needs to use 
> the plugin:
> > 
> > 
> >  
> > my-plugins
> > my-plugin
> > SNAPSHOT
> >   PLUGIN
> >  
> > 
> > Hope this helps,
> > 
> > Martin.
> > 
> > -Original Message-
> > From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
> > Sent: 03 March 2004 10:56
> > To: Maven Users List
> > Subject: Download of SNAPSHOT-Plugins
> > 
> > 
> > Hi,
> > 
> > by reading the Jelly script of the Plugin Plugin I figured 
> > out that if you
> > want to downlaod the current version of a plugin like this:
> > 
> > maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
> > -Dversion=1.2-SNAPSHOT 
> > 
> > and you already have a 1.2-SNAPSHOT version on your disk, it 
> > doesn't update
> > it with a newer version. As this is oky for non SNAPSHOT 
> > versions, I would
> > expect to SNAPSHOT behaviour for SNAPSHOT versions.
> > Is there any other elegant way to download and install the 
> > latest version of
> > a plugin with a SNAPSHOT version?
> > 
> > Joern
> > 
> > 
> -
> > 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: Building multiple jars with Maven

2004-03-03 Thread Jason van Zyl
On Tue, 2004-03-02 at 19:52, Brian Enigma wrote:

>  I am in the process of evaluating Maven to replace or coexist with  
> our existing Ant build process.  For final release projects, Maven is  
> great because I can tell it where to find mycompany-crypto.jar, etc.   
> For this core "util" project, I am having difficulty figuring out how  
> to best model the behavior I need in Maven.  Is there a way to have a  
> single project.xml output half a dozen jar files--one for each package?

This is something that is discouraged in Maven which is why there is
only one allowable entry for the source directory.

If you have multiple jars being output where each JAR addresses a
different concern then what Maven encourages is that you put these in
separate projects.

>   
>   Will I have to resort to multiple project files (project-crypto.xml,  
> project-xml.xml, etc) with one master project.xml to bind them all?

We don't consider this a "last resort", we consider this normal.

> Should I stick with the existing Ant scripts in this one case?

No, I would suggest you break up your build. But if you want to output
many JARs from one build then stick with Ant.

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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



Re: JDK 1.5 is out, and it breaks Maven

2004-03-03 Thread Berin Loritsch
Jörg Schaible wrote:
Hi Berin,

Jörg Schaible wrote on Wednesday, March 03, 2004 9:08 AM:

Berin Loritsch wrote on Tuesday, March 02, 2004 10:52 PM:

Thanks to the new JDK 1.5 installer, the default location to install
both the runtime and the developer kit is within the %PROGRAM_FILES%
directory.  That means a space is in the path to the "java" command
no matter how you slice it. 

The current "maven" script for Cygwin compatibility does not properly
handle this arrangement--because it never had to until now.  The
proper way to solve the issue is to add surrounding quotes to the
$JAVACMD that starts up maven. Enclosed is a script that works.
Berin,

can you raise an issue for the cli component:
http://jira.codehaus.org/secure/BrowseProject.jspa?id=> 10030


just saw that there is already an issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1179
can you attach the file there?


Thank you.  I created a new entry, and then I saw this message, so I
attached the fix in both places.  I also created a new entry for the
maven-java-plugin module to fix the compilation defaults issue.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Problem with assert in jellydoc

2004-03-03 Thread Tim Pizey
Hi, 

I am running out of cvs on my local machine 
but using 1.0-beta-9 on the production machine.
Both systems are running j2sdk1.4.2 

maven dist works on both

On the production machine maven site fails with 

[javadoc] 
/usr/local/packages/dist/SPIndent/build/org/paneris/spindent/set/quasi/TokenSet.java:128:
 
warning: as of release 1.4, assert is a keyword, and may not be used as an 
identifier
[javadoc] assert !(one instanceof ComplexTokenSet) || !(two instanceof 
ComplexTokenSet);
[javadoc] ^
[javadoc] 
/usr/local/packages/dist/SPIndent/build/org/paneris/spindent/set/quasi/TokenSet.java:128:
 
not a statement
[javadoc] assert !(one instanceof ComplexTokenSet) || !(two instanceof 
ComplexTokenSet);
[javadoc] ^
[javadoc] 
/usr/local/packages/dist/SPIndent/build/org/paneris/spindent/set/quasi/TokenSet.java:128:
 
';' expected
[javadoc] assert !(one instanceof ComplexTokenSet) || !(two instanceof 
ComplexTokenSet);
[javadoc]^

BUILD FAILED
null:37:50:  null:70:84:  Warning: Could not find file 
/usr/local/packages/dist/SPIndent/target/taglib.xml to copy.
Total time: 1 minutes 56 seconds

I have the following in project.properties
maven.compile.deprecation = on
maven.compile.optimize = off
maven.compile.debug = on
maven.compile.source = 1.4
maven.compile.target = 1.4
maven.javadoc.source = 1.4
maven.test.source = 1.4
maven.javadoc.customtags=todo 
todo.name=todo
todo.description="To Do:"


Any clues?

cheers
timp




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



Re: Melati version 0.7.2

2004-03-03 Thread Jason van Zyl
On Wed, 2004-03-03 at 06:04, Tim Pizey wrote:
> On Wednesday 03 March 2004 4:12 am, Jason van Zyl wrote:
> > On Tue, 2004-03-02 at 18:55, Tim Pizey wrote:
> > > Version 0.7.2 of Melati has been released.
> >
> > Why are you announcing this on the maven user list?
> 
> Because it is a Mavenised project and on the Maven powered by page ?
> 
> If this is not good I won't do it again. 

Probably not entirely appropriate here but something could be created
for announcements for Mavenized projects. That would be cool but I don't
think the maven user list is the place for it.

> yours
> Tim Pizey
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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



Re: Building multiple jars with Maven

2004-03-03 Thread Eric Giguere
Hi there
I would say if you like what Maven does and is, do the migration. I did 
it at my company. Basically, Maven is kind of a Super-Ant ( and much 
much more).

There are multiple ways to make Maven do what you need. By design, it 
produces one artifact per project, so you could for instance make one 
project per jar. Or, you could just migrate the existing Ant code and 
put it in your maven.xml with a new goal calling that code.

And if you migrate from an Ant based build system, I think you should 
know that your Ant script, as it is now, could be very easily integrated 
into Maven since any Ant targets can be called in a maven.xml script.

Hope it helps.
Eric.
Brian Enigma wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I searched through the maven-users archive for my question and  
found something close to what I am looking for  
(http://nagoya.apache.org/eyebrowse/ReadMsg? 
[EMAIL PROTECTED]&msgId=808818), but either it does not  
quite fit my scenario or I do not understand it as well as I think.

Anyway, I have a cvs project containing common utility source 
code  that gets used across a number of our projects.  This is all 
library  code--there is no main(), just a few unit tests.  This 
project includes  packages such as:

 com.mycompany.util.crypto
 com.mycompany.util.log
 com.mycompany.util.string
 com.mycompany.util.xml
 ...etc...
The ant script we currently employ builds multiple jar files from  
this source: mycompany-crypto.jar, mycompany-xml.jar, etc.  This has 
to  be done because of various legal reasons as well as minimizing the 
size  of distributed applications.  We do not want to build one 
gigantic util  jar file containing everything because we do not want 
to (or cannot)  ship the crypto classes to everyone.  Nor do we want 
to ship our custom  XML code out with a program that does not utilize 
it in order to  minimize download sizes as well as exposed object code 
(which can be  decompiled).

I am in the process of evaluating Maven to replace or coexist 
with  our existing Ant build process.  For final release projects, 
Maven is  great because I can tell it where to find 
mycompany-crypto.jar, etc.   For this core "util" project, I am having 
difficulty figuring out how  to best model the behavior I need in 
Maven.  Is there a way to have a  single project.xml output half a 
dozen jar files--one for each package?   Will I have to resort to 
multiple project files (project-crypto.xml,  project-xml.xml, etc) 
with one master project.xml to bind them all?   Should I stick with 
the existing Ant scripts in this one case?
 -Brian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFARSxR0dKNWt3rpSURAkx1AKDnfZtxf+mSCgPab23ZvA6P51UizwCgpEtI
PieRJxaq2YPkDKgWEX+0oaM=
=8J0h
-END PGP SIGNATURE-
-
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: Download of SNAPSHOT-Plugins

2004-03-03 Thread Martin Lambert
Hi Joern,

Glad I helped solve that problem. 

I am under the impression though that 'SNAPSHOT' in Maven is the latest development 
version. Fixed version numbers I believe are meant to represent stable versions of 
code. You appear to be muddying the waters with your versioning numbering system.

Cheers,

Martin.

-Original Message-
From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
Sent: 03 March 2004 11:52
To: Maven Users List
Subject: AW: Download of SNAPSHOT-Plugins


Hi Martin,

'1.2-SNAPSHOT' means that it is the version 1.2 of the plugin that is still
in development and changes until version 1.2 is released. And I wanted to
use 

maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
-Dversion=1.2-SNAPSHOT 

to download the latest version of the nightly build of that maven plugin.

But anyway, you helped me out with another problem I had with the versioning
of Maven plugins that are used to build an artifact. Until now I had a
proplem with building older versions of our project (e.g. for bug-fixing
branches). The source-code, project.xml etc. was revisioned in CVS, however
the versions of the plugins that were used to build the project are
mentioned nowhere. I.e. if you install a newer version of a plugin on your
computer it might screw up the original build. However, if you explicitely
write down in the project.xml the dependencies to the plugins you are using,
you can reproduce your revisioned project.

Joern

> -Ursprüngliche Nachricht-
> Von: Martin Lambert [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 3. März 2004 12:03
> An: Maven Users List
> Betreff: RE: Download of SNAPSHOT-Plugins
> 
> 
> Hi,
> 
> I'm not sure what you're on about with 1.2-SNAPSHOT, my 
> understanding is you either have 'SNAPSHOT' which will always 
> pull down the latest version or a fixed version number which 
> I guess Maven would see '1.2-SNAPSHOT' as.
> 
> Try this in the project.xml of a project that needs to use the plugin:
> 
> 
>  
> my-plugins
> my-plugin
> SNAPSHOT
> PLUGIN
>  
> 
> Hope this helps,
> 
> Martin.
> 
> -Original Message-
> From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
> Sent: 03 March 2004 10:56
> To: Maven Users List
> Subject: Download of SNAPSHOT-Plugins
> 
> 
> Hi,
> 
> by reading the Jelly script of the Plugin Plugin I figured 
> out that if you
> want to downlaod the current version of a plugin like this:
> 
> maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
> -Dversion=1.2-SNAPSHOT 
> 
> and you already have a 1.2-SNAPSHOT version on your disk, it 
> doesn't update
> it with a newer version. As this is oky for non SNAPSHOT 
> versions, I would
> expect to SNAPSHOT behaviour for SNAPSHOT versions.
> Is there any other elegant way to download and install the 
> latest version of
> a plugin with a SNAPSHOT version?
> 
> Joern
> 
> -
> 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]



AW: Download of SNAPSHOT-Plugins

2004-03-03 Thread Jörn Gebhardt
Hi Martin,

'1.2-SNAPSHOT' means that it is the version 1.2 of the plugin that is still
in development and changes until version 1.2 is released. And I wanted to
use 

maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
-Dversion=1.2-SNAPSHOT 

to download the latest version of the nightly build of that maven plugin.

But anyway, you helped me out with another problem I had with the versioning
of Maven plugins that are used to build an artifact. Until now I had a
proplem with building older versions of our project (e.g. for bug-fixing
branches). The source-code, project.xml etc. was revisioned in CVS, however
the versions of the plugins that were used to build the project are
mentioned nowhere. I.e. if you install a newer version of a plugin on your
computer it might screw up the original build. However, if you explicitely
write down in the project.xml the dependencies to the plugins you are using,
you can reproduce your revisioned project.

Joern

> -Ursprüngliche Nachricht-
> Von: Martin Lambert [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 3. März 2004 12:03
> An: Maven Users List
> Betreff: RE: Download of SNAPSHOT-Plugins
> 
> 
> Hi,
> 
> I'm not sure what you're on about with 1.2-SNAPSHOT, my 
> understanding is you either have 'SNAPSHOT' which will always 
> pull down the latest version or a fixed version number which 
> I guess Maven would see '1.2-SNAPSHOT' as.
> 
> Try this in the project.xml of a project that needs to use the plugin:
> 
> 
>  
> my-plugins
> my-plugin
> SNAPSHOT
> PLUGIN
>  
> 
> Hope this helps,
> 
> Martin.
> 
> -Original Message-
> From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
> Sent: 03 March 2004 10:56
> To: Maven Users List
> Subject: Download of SNAPSHOT-Plugins
> 
> 
> Hi,
> 
> by reading the Jelly script of the Plugin Plugin I figured 
> out that if you
> want to downlaod the current version of a plugin like this:
> 
> maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
> -Dversion=1.2-SNAPSHOT 
> 
> and you already have a 1.2-SNAPSHOT version on your disk, it 
> doesn't update
> it with a newer version. As this is oky for non SNAPSHOT 
> versions, I would
> expect to SNAPSHOT behaviour for SNAPSHOT versions.
> Is there any other elegant way to download and install the 
> latest version of
> a plugin with a SNAPSHOT version?
> 
> Joern
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


Re: SNMP jar on ibilio repository

2004-03-03 Thread nicolas De Loof
Thank you, I'll take a look at this.

Thanks to Emmanuel too for uploading westhawk's stack.

Nico.

Ben Walding a écrit :

Another one to consider is joe-snmp contained inside opennms

They weren't releasing it as a separate jar last time I looked, but I 
did compile a snapshot onto ibiblio.  Might be worth hassling them to 
get it released separately if anyone else has interest in it.

http://www.ibiblio.org/maven/opennms/jars/

(I packaged it up for a guy at work, the feedback he gave me was that 
it was quite extensible and easy to use - we now use it to poll over 
300 devices across the state every 24 hours)

Cheers,

Ben

nicolas De Loof wrote:

Please can someone upload the SNMP stack from 
http://snmp.westhawk.co.uk/ on maven ibiblio repository,
(or suggest me another SNMP implementation to use ?)

Thank you.

Nico.

-
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: SNMP jar on ibiblio

2004-03-03 Thread Emmanuel Venisse
Done in westhawk group.

Could you add a request in Jira the next time?
Thanks

Emmanuel

- Original Message - 
From: "nicolas De Loof" <[EMAIL PROTECTED]>
To: "Maven Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, March 03, 2004 11:10 AM
Subject: SNMP jar on ibiblio


> Please can someone upload the SNMP stack from 
> http://snmp.westhawk.co.uk/ on maven ibiblio repository,
> (or suggest me another SNMP implementation to use ?)
> 
> Thank you.
> 
> Nico.
> 
> -
> 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: SNMP jar on ibilio repository

2004-03-03 Thread Ben Walding
Another one to consider is joe-snmp contained inside opennms

They weren't releasing it as a separate jar last time I looked, but I 
did compile a snapshot onto ibiblio.  Might be worth hassling them to 
get it released separately if anyone else has interest in it.

http://www.ibiblio.org/maven/opennms/jars/

(I packaged it up for a guy at work, the feedback he gave me was that it 
was quite extensible and easy to use - we now use it to poll over 300 
devices across the state every 24 hours)

Cheers,

Ben

nicolas De Loof wrote:

Please can someone upload the SNMP stack from 
http://snmp.westhawk.co.uk/ on maven ibiblio repository,
(or suggest me another SNMP implementation to use ?)

Thank you.

Nico.

-
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]


Inconsistent artifact deployment method across plugins

2004-03-03 Thread Charles Blaxland
Hi,

The various maven plugins are inconsistent in the way they deploy 
artifacts to the remote repository.  They use, variously, 
artifact:deploy or deply:artifact, for example:

war:deploy  -> artifact:deploy
ejb:deploy  -> artifact:deploy
jar:deploy  -> deploy:artifact
dist:deploy -> deploy:artifact
Is there any particular reason for this?  It'd be great to see all 
plugins standardized to use artifact:deploy to provide more flexibility 
in choosing the deployment method (eg: ftp).  We're running Windows 
exclusively here, so simply using FTP is a lot less pain than having to 
install and configure ssh servers/clients.

Along the same lines, an ftp option for site:deploy would be nice.

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


Re: Melati version 0.7.2

2004-03-03 Thread Tim Pizey
On Wednesday 03 March 2004 4:12 am, Jason van Zyl wrote:
> On Tue, 2004-03-02 at 18:55, Tim Pizey wrote:
> > Version 0.7.2 of Melati has been released.
>
> Why are you announcing this on the maven user list?

Because it is a Mavenised project and on the Maven powered by page ?

If this is not good I won't do it again. 

yours
Tim Pizey


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



RE: Download of SNAPSHOT-Plugins

2004-03-03 Thread Martin Lambert
Hi,

I'm not sure what you're on about with 1.2-SNAPSHOT, my understanding is you either 
have 'SNAPSHOT' which will always pull down the latest version or a fixed version 
number which I guess Maven would see '1.2-SNAPSHOT' as.

Try this in the project.xml of a project that needs to use the plugin:


 
my-plugins
my-plugin
SNAPSHOT
  PLUGIN
 

Hope this helps,

Martin.

-Original Message-
From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
Sent: 03 March 2004 10:56
To: Maven Users List
Subject: Download of SNAPSHOT-Plugins


Hi,

by reading the Jelly script of the Plugin Plugin I figured out that if you
want to downlaod the current version of a plugin like this:

maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
-Dversion=1.2-SNAPSHOT 

and you already have a 1.2-SNAPSHOT version on your disk, it doesn't update
it with a newer version. As this is oky for non SNAPSHOT versions, I would
expect to SNAPSHOT behaviour for SNAPSHOT versions.
Is there any other elegant way to download and install the latest version of
a plugin with a SNAPSHOT version?

Joern

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



Download of SNAPSHOT-Plugins

2004-03-03 Thread Jörn Gebhardt
Hi,

by reading the Jelly script of the Plugin Plugin I figured out that if you
want to downlaod the current version of a plugin like this:

maven plugin:download -DartifactId=my-plugin -DgroupId=my-plugins
-Dversion=1.2-SNAPSHOT 

and you already have a 1.2-SNAPSHOT version on your disk, it doesn't update
it with a newer version. As this is oky for non SNAPSHOT versions, I would
expect to SNAPSHOT behaviour for SNAPSHOT versions.
Is there any other elegant way to download and install the latest version of
a plugin with a SNAPSHOT version?

Joern


SNMP jar on ibiblio

2004-03-03 Thread nicolas De Loof
Please can someone upload the SNMP stack from 
http://snmp.westhawk.co.uk/ on maven ibiblio repository,
(or suggest me another SNMP implementation to use ?)

Thank you.

Nico.

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


SNMP jar on ibilio repository

2004-03-03 Thread nicolas De Loof
Please can someone upload the SNMP stack from 
http://snmp.westhawk.co.uk/ on maven ibiblio repository,
(or suggest me another SNMP implementation to use ?)

Thank you.

Nico.

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


RE: JDK 1.5 is out, and it breaks Maven

2004-03-03 Thread Jörg Schaible
Hi Berin,

Jörg Schaible wrote on Wednesday, March 03, 2004 9:08 AM:
> Berin Loritsch wrote on Tuesday, March 02, 2004 10:52 PM:
>> Thanks to the new JDK 1.5 installer, the default location to install
>> both the runtime and the developer kit is within the %PROGRAM_FILES%
>> directory.  That means a space is in the path to the "java" command
>> no matter how you slice it. 
>> 
>> The current "maven" script for Cygwin compatibility does not properly
>> handle this arrangement--because it never had to until now.  The
>> proper way to solve the issue is to add surrounding quotes to the
>> $JAVACMD that starts up maven. Enclosed is a script that works.
> 
> Berin,
> 
> can you raise an issue for the cli component:
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=> 10030

just saw that there is already an issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1179

can you attach the file there?

Regards,
Jörg

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



RE: JDK 1.5 is out, and it breaks Maven

2004-03-03 Thread Jörg Schaible
Berin Loritsch wrote on Tuesday, March 02, 2004 10:52 PM:
> Thanks to the new JDK 1.5 installer, the default location to
> install both the runtime and the developer kit is within the
> %PROGRAM_FILES% directory.  That means a space is in the path
> to the "java" command no matter how you slice it.
> 
> The current "maven" script for Cygwin compatibility does not
> properly handle this arrangement--because it never had to
> until now.  The proper way to solve the issue is to add
> surrounding quotes to the $JAVACMD that starts up maven.
> Enclosed is a script that works.

Berin,

can you raise an issue for the cli component:
http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030

Regards,
Jörg

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