runtime inspection of release info

2003-10-15 Thread Marc Portier
Hi all,

I want to achieve the following:
- have an easy mechanism for applications to be able to inspect their 
own release information at runtime... (think about: help/about dialogs 
or log statements showing some release info)

(the info to gather would be the kind of stuf inside the manifest.mf file)

I was thinking of the following approach:
- generate just before compilation a class myproject.package.ReleaseInfo 
that holds the info hardcoded

before delving into it deaper I was hoping one of you could tell me:
1/ it's already done (couldn't find it)
2/ euh, a number of reasons not to get to do it ;-)
3/ sensible suggestions towards just doing it
regards and thx
-marc=
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java  XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


jelly variable $sourcesPresent in maven-java-plugin-1.3

2003-10-15 Thread Heiko Kundlacz
Hi all,

Currently I check how to work with jelly from maven. I have had a look 
at plugin.jelly and found:

..
j:when test=${sourcesPresent == 'true'}
..
I can't understand where the variable sourcesPresent was set. Could you 
please explain it to me?

Thanks for your help

Heiko

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


RE: runtime inspection of release info

2003-10-15 Thread Mike Gilbert
Hi Marc,

have a look at
http://java.sun.com/products/jdk/1.2/docs/guide/versioning/spec/VersioningSp
ecification.html#PackageVersioning

and

http://java.sun.com/j2se/1.4.1/docs/api/java/lang/Package.html


 -Original Message-
 From: Marc Portier [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, October 15, 2003 8:04 AM
 To: 'Maven Users List'
 Subject: runtime inspection of release info


 Hi all,

 I want to achieve the following:
 - have an easy mechanism for applications to be able to inspect their
 own release information at runtime... (think about:
 help/about dialogs
 or log statements showing some release info)

 (the info to gather would be the kind of stuf inside the
 manifest.mf file)


 I was thinking of the following approach:
 - generate just before compilation a class
 myproject.package.ReleaseInfo
 that holds the info hardcoded


 before delving into it deaper I was hoping one of you could tell me:
 1/ it's already done (couldn't find it)
 2/ euh, a number of reasons not to get to do it ;-)
 3/ sensible suggestions towards just doing it

 regards and thx
 -marc=
 --
 Marc Portierhttp://outerthought.org/
 Outerthought - Open Source, Java  XML Competence Support Center
 Read my weblog at  http://radio.weblogs.com/0116284/
 [EMAIL PROTECTED]  [EMAIL PROTECTED]


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

 ---
 Incoming mail is certified Virus Free.
 Checked by AVG anti-virus system (http://www.grisoft.com).
 Version: 6.0.525 / Virus Database: 322 - Release Date: 09/10/2003


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.525 / Virus Database: 322 - Release Date: 09/10/2003



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



Help needed in writing custom Jelly tags

2003-10-15 Thread Sri Sankaran
Have you written a custom Jelly tag library - that is *not* part of the Maven 
installation?

If so, how do you specify the name of your TagLibrary class in the xmlns declaration?  
I am finding that 

  xmlns:mine=jelly:com.foo.bar.MyTagLibrary

doesn't cut it.  I am having a devil of a time (see numerous threads in the past 
several days with my name!) getting past a ClassNotFoundException.

The o.a.commons.jelly.parse.XMLParser fails in its attempt to find the TagLibrary 
class even though it is using the root.maven class loader and the dependency on the 
tag library (in the project.xml) indicates that the root.maven class loader should be 
used to load the classes in the tag library jar.

Sri



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



Re: same project, different properties

2003-10-15 Thread Nicolas De Loof
I tried this too, and it doesn't work :


?xml version=1.0 encoding=ISO-8859-1?
project
xmlns:j=jelly:core

extendproject.xml/extend
idpacila-back-office/id
namepacila-back-office/name
groupIdpacila/groupId

j:set var=maven.war.webxml value=web-back-office.xml /

/project

Nico.


- Original Message - 
From: Nicolas De Loof [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 3:19 PM
Subject: same project, different properties


 Hello all,

 I'm a newbie maven user.

 I use maven for a webapp project, and I need to build a second war file from the 
 same java sources (same web
 application, but different web.xml)

 I want to use war-plugin maven.war.webxml property to set the web.xml that is used 
 in the war, and change it
regarding
 wich war must be build.

 Is there any way to change the propect.properties that is used when runnign maven or 
 to set properties in project.xml
?

 I tried to set a second project.xml that extends my project.xml this way :

 ?xml version=1.0 encoding=ISO-8859-1?
 project
 extendproject.xml/extend
 idrestricted-webapp/id
 namerestricted-webapp/name
 groupIdwebapp/groupId

 properties
 maven.war.webxmlweb-restricted.xml/maven.war.webxml
 /properties
 /project

 This way I should be able to use maven -p option to run a build on my second webapp. 
 But this doesn't work (default
 web.xml is used).

 Do you have any suggestion ?

 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: same project, different properties

2003-10-15 Thread Nicolas . CHALUMEAU
Nicolas, you could make 2 subprojects, it is so simple to do ;) and a good 
approche

And see the WhyYouCantCreateMultipleArtifactsInOneProject page.
http://wiki.codehaus.org/maven/WhyYouCantCreateMultipleArtifactsInOneProject

Nicolas

---




Nicolas De Loof [EMAIL PROTECTED]
15/10/2003 15:19
Veuillez répondre à Maven Users List

 
Pour :  [EMAIL PROTECTED]
cc : 
Objet : same project, different properties


Hello all,

I'm a newbie maven user.

I use maven for a webapp project, and I need to build a second war file 
from the same java sources (same web
application, but different web.xml)

I want to use war-plugin maven.war.webxml property to set the web.xml 
that is used in the war, and change it regarding
wich war must be build.

Is there any way to change the propect.properties that is used when 
runnign maven or to set properties in project.xml ?

I tried to set a second project.xml that extends my project.xml this way :

?xml version=1.0 encoding=ISO-8859-1?
project
extendproject.xml/extend
idrestricted-webapp/id
namerestricted-webapp/name
groupIdwebapp/groupId

properties
maven.war.webxmlweb-restricted.xml/maven.war.webxml
/properties
/project

This way I should be able to use maven -p option to run a build on my 
second webapp. But this doesn't work (default
web.xml is used).

Do you have any suggestion ?

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: Property inheritance

2003-10-15 Thread Alastair Rodgers
Thanks - I wasn't aware of MAVEN_HOME_LOCAL. 


 -Original Message-
 From: khote [mailto:[EMAIL PROTECTED] 
 Sent: 15 October 2003 13:04
 To: Maven Users List
 Subject: Re: Property inheritance
 
 
 set a global
 export MAVEN_HOME_LOCAL=/mavenrepository
 or some such place.  Put that in your /etc/profile so 
 everybody shares it.
 
 - Original Message - 
 From: Alastair Rodgers [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, October 15, 2003 3:46 AM
 Subject: Property inheritance
 
 
  Hello,
 
  I've just started using Maven over the last couple of days, 
 and I must
 say, my first impressions are very positive (I'm used to 
 dealing with lots of nearly-identical Ant scripts!). Thanks.
 
  I've been trying to use property inheritance, and I 
 gathered from the
 mailing list archive that project.properties  
 build.properties aren't inherited. I tried to get round this 
 by creating a global.properties file and manually loading the 
 properties from it in my base maven.xml:
 
jelly-core:set var=project.root
 value=${pom.parentBasedir().getParentFile().getCanonicalFile()}/
jelly-util:properties 
  file=${project.root}/etc/global.properties/
 
  In global.properties I have:
 
maven.repo.local=/usr/local/data/maven/repository
 
  I then have a sub-project which inherits from this base. If 
 I run, say
 maven jar on the sub-project and dump the value of 
 maven.repo.local to the console from the sub-project's 
 maven.xml, I find it has the desired value (from 
 global.properties). However, Maven is still actually using 
 the default repository (/home/user/.maven/repository to do 
 the build) - e.g. if I delete this dir, Maven creates it and 
 starts downloading all the jars again.
 
  Is there a way round this problem?
 
  Thanks,
  Al.
 
 
 
 
 -
 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: same project, different properties

2003-10-15 Thread Nicolas De Loof
I agree with it, but I don't know how to do it. The only differences between the two 
webapps will be the URI it will
accept, that are configured in web deployment descriptor.

How can I make such subprojects (if it's really so simple) ?


As a second general question, what is the use of the properties section if it 
doesn't set maven properties ?


Thank you for helping me !

Nico.



- Original Message - 
From: [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 3:27 PM
Subject: Re: same project, different properties


Nicolas, you could make 2 subprojects, it is so simple to do ;) and a good
approche

And see the WhyYouCantCreateMultipleArtifactsInOneProject page.
http://wiki.codehaus.org/maven/WhyYouCantCreateMultipleArtifactsInOneProject

Nicolas

---




Nicolas De Loof [EMAIL PROTECTED]
15/10/2003 15:19
Veuillez répondre à Maven Users List


Pour :  [EMAIL PROTECTED]
cc :
Objet : same project, different properties


Hello all,

I'm a newbie maven user.

I use maven for a webapp project, and I need to build a second war file
from the same java sources (same web
application, but different web.xml)

I want to use war-plugin maven.war.webxml property to set the web.xml
that is used in the war, and change it regarding
wich war must be build.

Is there any way to change the propect.properties that is used when
runnign maven or to set properties in project.xml ?

I tried to set a second project.xml that extends my project.xml this way :

?xml version=1.0 encoding=ISO-8859-1?
project
extendproject.xml/extend
idrestricted-webapp/id
namerestricted-webapp/name
groupIdwebapp/groupId

properties
maven.war.webxmlweb-restricted.xml/maven.war.webxml
/properties
/project

This way I should be able to use maven -p option to run a build on my
second webapp. But this doesn't work (default
web.xml is used).

Do you have any suggestion ?

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]



How to fail inside a maven plugin

2003-10-15 Thread emmanuel . boudrant
Hi there,

How to fail inside a maven plugin ?

example:

goal name=init

j:set var=errorfalse/j:set
j:if test=${class.dir == null}
ant:echo message=property 'class.dir' not present/
j:set var=errortrue/j:set
/j:if
j:if test=${error == 'true'}
ant:echo message=Missing properties !/
FAIL HERE
/j:if
...
/goal

Thx,
-emmanuel

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



Re: How to fail inside a maven plugin

2003-10-15 Thread khote
fail message=some message/
or 
fail
some message
/fail
- Original Message - 
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 7:03 AM
Subject: How to fail inside a maven plugin


 Hi there,
 
 How to fail inside a maven plugin ?
 
 example:
 
   goal name=init
   
   j:set var=errorfalse/j:set
   j:if test=${class.dir == null}
 ant:echo message=property 'class.dir' not present/
 j:set var=errortrue/j:set
 /j:if
 j:if test=${error == 'true'}
 ant:echo message=Missing properties !/
 FAIL HERE
 /j:if
   ...
   /goal
 
 Thx,
 -emmanuel
 
 -
 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]



Réf. : How to fail inside a maven plugin

2003-10-15 Thread Nicolas . CHALUMEAU
Acording to the ant docs

fail/ 
or 
fail message=Something wrong here./ 
or 
failSomething wrong here./fail

Nicolas





[EMAIL PROTECTED]
15/10/2003 16:03
Veuillez répondre à Maven Users List

 
Pour :  [EMAIL PROTECTED]
cc : 
Objet : How to fail inside a maven plugin


Hi there,

How to fail inside a maven plugin ?

example:

 goal name=init
 
 j:set var=errorfalse/j:set
 j:if test=${class.dir == null}
 ant:echo message=property 
'class.dir' not present/
 j:set 
var=errortrue/j:set
 /j:if
 j:if test=${error == 'true'}
 ant:echo 
message=Missing properties !/
 FAIL HERE
 /j:if
 ...
 /goal

Thx,
-emmanuel

-
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 fail inside a maven plugin

2003-10-15 Thread Mike Gilbert
 -Original Message-
 
 Hi there,
 
 How to fail inside a maven plugin ?
 
 example:
 
   goal name=init
   
   j:set var=errorfalse/j:set
   j:if test=${class.dir == null}
   ant:echo message=property 'class.dir' 
 not present/
   j:set var=errortrue/j:set
   /j:if
   j:if test=${error == 'true'}
   ant:echo message=Missing properties !/
   FAIL HERE


ant:failMissing properties !/ant:fail



   /j:if
   ...
   /goal
 
 Thx,
 -emmanuel
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 ---
 Incoming mail is certified Virus Free.
 Checked by AVG anti-virus system (http://www.grisoft.com).
 Version: 6.0.525 / Virus Database: 322 - Release Date: 09/10/2003
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.525 / Virus Database: 322 - Release Date: 09/10/2003
 


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



How to check in a property is setted

2003-10-15 Thread emmanuel . boudrant


Hi there,

Ho ca I check if a property is setted in project.properties (or
~/build.properties...).

This is not working : 

j:if test=${msl.dir == null} ... /j:if

Thx,
-emmanuel

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



RE: How to fail inside a maven plugin

2003-10-15 Thread Vincent Massol
I guess that if you're asking, it's because ant:fail doesn't work?

-Vincent

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: 15 October 2003 16:04
 To: [EMAIL PROTECTED]
 Subject: How to fail inside a maven plugin
 
 Hi there,
 
 How to fail inside a maven plugin ?
 
 example:
 
   goal name=init
 
   j:set var=errorfalse/j:set
   j:if test=${class.dir == null}
   ant:echo message=property 'class.dir' not
present/
   j:set var=errortrue/j:set
   /j:if
   j:if test=${error == 'true'}
   ant:echo message=Missing properties !/
   FAIL HERE
   /j:if
   ...
   /goal
 
 Thx,
 -emmanuel
 
 -
 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 fail inside a maven plugin

2003-10-15 Thread khote
when I want to see how maven and ant work together, I look in the plugins.
My repository is in /mavenrepository

I do things like:

grep -ir fail /mavenrepository/ | less

and I can see where the plugin.jelly files are using that word.

- Original Message - 
From: [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 7:41 AM
Subject: RE: How to fail inside a maven plugin


 
 It's because I was thinking the 'fail' exist in Maven or Jetty... ;)
 
 ant:fail work fine ;)
 
 Thx,
 -emmanuel
 
 Selon Vincent Massol [EMAIL PROTECTED]:
 
  I guess that if you're asking, it's because ant:fail doesn't work?
  
  -Vincent
  
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
   Sent: 15 October 2003 16:04
   To: [EMAIL PROTECTED]
   Subject: How to fail inside a maven plugin
   
   Hi there,
   
   How to fail inside a maven plugin ?
   
   example:
   
 goal name=init
   
 j:set var=errorfalse/j:set
 j:if test=${class.dir == null}
   ant:echo message=property 'class.dir' not
  present/
   j:set var=errortrue/j:set
   /j:if
   j:if test=${error == 'true'}
   ant:echo message=Missing properties !/
   FAIL HERE
   /j:if
 ...
 /goal
   
   Thx,
   -emmanuel
   
   -
   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 check in a property is setted

2003-10-15 Thread Dominik Dahlem
I had the same problem a while ago. I solved it with reading the
properties in a jelly variable
j:set var=mslDir value=${msl.dir} /

You can then ckeck if it is set to null.

Hope that helps,
Dominik



On Wed, 2003-10-15 at 15:36, [EMAIL PROTECTED] wrote:
 Hi there,
 
 Ho ca I check if a property is setted in project.properties (or
 ~/build.properties...).
 
 This is not working : 
 
 j:if test=${msl.dir == null} ... /j:if
 
 Thx,
 -emmanuel
 
 -
 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 check in a property is setted

2003-10-15 Thread Marc Portier
not sure, (quite new to maven too)

I've been checking some existing jelly code the last days and have seen 
this construct quite often:

  j:if test=${!empty(msl.dir)}

sounds like it is your way to go?

regards,
-marc=
[EMAIL PROTECTED] wrote:
Hi there,

Ho ca I check if a property is setted in project.properties (or
~/build.properties...).
This is not working : 

j:if test=${msl.dir == null} ... /j:if

Thx,
-emmanuel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java  XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: How to check in a property is setted

2003-10-15 Thread khote
j:if test=${empty(msl.dir) == 'true'} 
j:if test=${empty(msl.dir) != 'true'} 
 
j:if test=${!empty(msl.dir) == 'true'} 



- Original Message - 
From: Marc Portier [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 7:51 AM
Subject: Re: How to check in a property is setted


 not sure, (quite new to maven too)
 
 I've been checking some existing jelly code the last days and have seen 
 this construct quite often:
 
j:if test=${!empty(msl.dir)}
 
 sounds like it is your way to go?
 
 regards,
 -marc=
 
 
 [EMAIL PROTECTED] wrote:
  
  Hi there,
  
  Ho ca I check if a property is setted in project.properties (or
  ~/build.properties...).
  
  This is not working : 
  
  j:if test=${msl.dir == null} ... /j:if
  
  Thx,
  -emmanuel
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 -- 
 Marc Portierhttp://outerthought.org/
 Outerthought - Open Source, Java  XML Competence Support Center
 Read my weblog at  http://radio.weblogs.com/0116284/
 [EMAIL PROTECTED]  [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]



multiproject using goal dist

2003-10-15 Thread Howard M. Lewis Ship
I'm trying to whip together something so that I can support binary and source distros 
for my
project.

What I thought I would do is invoke dist in each sub-project, and add a postGoal to 
copy the
distros up to a directory of my master project.

First step is to see what dist does in this context ... 

bash-2.05b$ maven multiproject:goal -Dgoal=dist
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc1-SNAPSHOT

Starting the reactor...
Our processing order:
HiveMind Framework
HiveMind Library
+
| Executing dist HiveMind Framework
| Memory: 3M/11M
+
multiproject:goal:
Overriding previous definition of reference to clover.classpath
dist:build-setup:
[mkdir] Created dir: C:\workspace\hivemind\framework\target\distributions

xdoc:init:

java:prepare-filesystem:

java:compile:
[echo] Compiling to c:\workspace\hivemind\framework/target/classes

java:jar-resources:

test:prepare-filesystem:

. . .

javadoc:generate:

dist:prepare-bin-filesystem:
[mkdir] Created dir:
C:\workspace\hivemind\framework\target\commons-hivemind-1.0-alpha-3\bin\commons-hivemind-1.0-alpha-3
[echo]
  +---+
  | C R E A T I N G  B I N A R Y  D I S T R I B U T I O N |
  +---+

[copy] Copying 1 file to
C:\workspace\hivemind\framework\target\commons-hivemind-1.0-alpha-3\bin\commons-hivemind-1.0-alpha-3
[copy] Copying 880 files to
C:\workspace\hivemind\framework\target\commons-hivemind-1.0-alpha-3\bin\commons-hivemind-1.0-alpha-3
\docs

dist:build-bin:
[tar] Building tar:
C:\workspace\hivemind\framework\target\distributions\commons-hivemind-1.0-alpha-3.tar
[gzip] Building:
C:\workspace\hivemind\framework\target\distributions\commons-hivemind-1.0-alpha-3.tar.gz
[delete] Deleting:
C:\workspace\hivemind\framework\target\distributions\commons-hivemind-1.0-alpha-3.tar
[zip] Building zip:
C:\workspace\hivemind\framework\target\distributions\commons-hivemind-1.0-alpha-3.zip

dist:prepare-src-filesystem:
[mkdir] Created dir:
C:\workspace\hivemind\framework\target\commons-hivemind-1.0-alpha-3\src\commons-hivemind-1.0-alpha-3
[echo]
  +---+
  | C R E A T I N G  S O U R C E  D I S T R I B U T I O N |
  +---+

[copy] Copying 3 files to
C:\workspace\hivemind\framework\target\commons-hivemind-1.0-alpha-3\src\commons-hivemind-1.0-alpha-3

BUILD FAILED
File.. file:/C:/Documents and
Settings/Howard/.maven/plugins/maven-multiproject-plugin-1.1-SNAPSHOT/
Element... maven:reactor
Line.. 174
Column 9
Unable to obtain goal [dist:prepare-src-filesystem] -- file:/C:/Documents and
Settings/Howard/.maven/plugins/maven-dist-plugin-1.3-SNAPSHOT/:106:62: ant:move 
Warning: Could
not find file C:\workspace\hivemind\framework\build.xml to copy.
Total time: 2 minutes 4 seconds
Finished at: Wed Oct 15 10:52:28 EDT 2003

bash-2.05b$


I looked at the code referenced in the error:

ant:available property=maven.dist.build.xml.avail
   file=${basedir}/build.xml/

j:choose
  j:when test=${maven.dist.build.xml.avail}
ant:copy todir=${maven.dist.src.assembly.dir} file=build.xml/
  /j:when
  j:otherwise
attainGoal name=ant:generate-build/
ant:move 
  file=build.xml
  tofile=${maven.dist.src.assembly.dir}/build.xml/
  /j:otherwise
/j:choose

Strangely, the output doesn't indicate that ant:generate-build goal was
attained/executed/whatever, so you can see why the generated build.xml would be 
missing. Any
suggestions?

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com


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



RE: How to fail inside a maven plugin

2003-10-15 Thread Vincent Massol


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: 15 October 2003 16:42
 To: Maven Users List
 Subject: RE: How to fail inside a maven plugin
 
 
 It's because I was thinking the 'fail' exist in Maven or Jetty... ;)

  ^^^
you're doing too much web development ;-)

-Vincent

[snip]


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



Re: How to check in a property is setted [found]

2003-10-15 Thread emmanuel . boudrant

No, it's 

j:if test=${context.getVariable('msl.dir') == null}

Thx,
-emmanuel

Selon khote [EMAIL PROTECTED]:

 j:if test=${empty(msl.dir) == 'true'} 
 j:if test=${empty(msl.dir) != 'true'} 
  
 j:if test=${!empty(msl.dir) == 'true'} 
 
 
 
 - Original Message - 
 From: Marc Portier [EMAIL PROTECTED]
 To: Maven Users List [EMAIL PROTECTED]
 Sent: Wednesday, October 15, 2003 7:51 AM
 Subject: Re: How to check in a property is setted
 
 
  not sure, (quite new to maven too)
  
  I've been checking some existing jelly code the last days and have seen 
  this construct quite often:
  
 j:if test=${!empty(msl.dir)}
  
  sounds like it is your way to go?
  
  regards,
  -marc=
  
  
  [EMAIL PROTECTED] wrote:
   
   Hi there,
   
   Ho ca I check if a property is setted in project.properties (or
   ~/build.properties...).
   
   This is not working : 
   
   j:if test=${msl.dir == null} ... /j:if
   
   Thx,
   -emmanuel
   
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
   
  
  -- 
  Marc Portierhttp://outerthought.org/
  Outerthought - Open Source, Java  XML Competence Support Center
  Read my weblog at  http://radio.weblogs.com/0116284/
  [EMAIL PROTECTED]  [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]



context, pom ...?

2003-10-15 Thread emmanuel . boudrant


Hi,

What are the object context, pom (ex: ${context.getVariable(...)})
Is there any documentation about them ?

Thx,
-emmanuel

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



Re: Uploading POM's into the repository working or declined?

2003-10-15 Thread Paul Libbrecht
Rademacher Tobias wrote:
Hi Folks,

Does the RC1 release uploads the the POM files into the repository? I read a
discussion thread on the maven mailing lists about this topic a couple of
months ago. So please do not flame me when you decided to decline this
feature request.
Assuming that it works I have a related question: Is it possible to load a
diffenrent POM from a XML file in order to process it? It would be cool if
we would be able to access repository POM's _and_ interspect there
dependencies.
Any thoughts

Toby
This would have another nice aspect: check-out the project's current 
tree. Or... offer a view to the source of a dependency within an IDE... 
but this may all be future.

Paul

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


RE: runtime inspection of release info

2003-10-15 Thread Sonnek, Ryan
Sorry about the OT question, but how did you extract the
implementation-version info?  Running in winxp, suns' sdk 1.4.2, I get null
whenever I try to get the info.  Maven built the manifest correctly, but my
app can't get the info.  Here's what I've tried:

//these two give me null for the implementation version
MyClass.class.getPackage().getImplementationVersion();
this.getClass().getPackage().getImplementationVersion();

//this gives me a NPE on the getPackage() call.
Package.getPackage(maven version info).getImplementationVersion();


I've gone through several forums enteries, but haven't got code working so
far.  Appreciate any help or direction!

Ryan

-Original Message-
From: Marc Portier [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 15, 2003 6:37 AM
To: Maven Users List
Subject: Re: runtime inspection of release info

wow, thx Mike, was indeed what I was looking for.
looks like another one of the well kept secrets of java.lang.* :-)

-marc=

Mike Gilbert wrote:

 Hi Marc,
 
 have a look at

http://java.sun.com/products/jdk/1.2/docs/guide/versioning/spec/VersioningSp
 ecification.html#PackageVersioning
 
 and
 
 http://java.sun.com/j2se/1.4.1/docs/api/java/lang/Package.html
 
 
 
-Original Message-
From: Marc Portier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 8:04 AM
To: 'Maven Users List'
Subject: runtime inspection of release info


Hi all,

I want to achieve the following:
- have an easy mechanism for applications to be able to inspect their
own release information at runtime... (think about:
help/about dialogs
or log statements showing some release info)

(the info to gather would be the kind of stuf inside the
manifest.mf file)


I was thinking of the following approach:
- generate just before compilation a class
myproject.package.ReleaseInfo
that holds the info hardcoded


before delving into it deaper I was hoping one of you could tell me:
1/ it's already done (couldn't find it)
2/ euh, a number of reasons not to get to do it ;-)
3/ sensible suggestions towards just doing it

regards and thx
-marc=
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java  XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]


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

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.525 / Virus Database: 322 - Release Date: 09/10/2003

 
 
 ---
 Outgoing mail is certified Virus Free.
 Checked by AVG anti-virus system (http://www.grisoft.com).
 Version: 6.0.525 / Virus Database: 322 - Release Date: 09/10/2003
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

-- 
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java  XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [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: Property inheritance

2003-10-15 Thread Paul Libbrecht
I've found it easier to simply add in a common bin directory, a modified 
copy of the maven script with the added properties.

Paul

khote wrote:
set a global
export MAVEN_HOME_LOCAL=/mavenrepository
or some such place.  Put that in your /etc/profile so everybody shares it.
- Original Message - 
From: Alastair Rodgers [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 3:46 AM
Subject: Property inheritance



Hello,

I've just started using Maven over the last couple of days, and I must
say, my first impressions are very positive (I'm used to dealing with lots
of nearly-identical Ant scripts!). Thanks.
I've been trying to use property inheritance, and I gathered from the
mailing list archive that project.properties  build.properties aren't
inherited. I tried to get round this by creating a global.properties file
and manually loading the properties from it in my base maven.xml:
 jelly-core:set var=project.root
value=${pom.parentBasedir().getParentFile().getCanonicalFile()}/

 jelly-util:properties file=${project.root}/etc/global.properties/

In global.properties I have:

 maven.repo.local=/usr/local/data/maven/repository

I then have a sub-project which inherits from this base. If I run, say
maven jar on the sub-project and dump the value of maven.repo.local to the
console from the sub-project's maven.xml, I find it has the desired value
(from global.properties). However, Maven is still actually using the default
repository (/home/user/.maven/repository to do the build) - e.g. if I
delete this dir, Maven creates it and starts downloading all the jars again.
Is there a way round this problem?

Thanks,
Al.



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


Use another file instead of ${user.home}/build.properties

2003-10-15 Thread Martin Skopp
Hi gurus,

I like to use another file instead ${user.home}/build.properties.
Is there any way to specify a alternative filename e.g. on the maven CLI
or by a system property 
(e.g. maven -Duser.properties.file=C:\maven.build.properties) ?

I have the problem here that build.properties as filename is already in
use

Thanks for info,
-- 
Martin Skopp
Riege Software International GmbH
Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com
 
This email is intended to be viewed with a nonproportional font.
Public Key on http://www.keyserver.net, Key-ID: 3D4027B5
Fingerprint: 1970 C78D 9A1D 99FA 5CE4  5C0D 29E6 6A95 3D40 27B5



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



Multiproject

2003-10-15 Thread Dahlen Jr, Shawn M
Hello -

I'm attempting to use the multiproject plugin to generate a website and I continually 
recieve
the following error:

BUILD FAILED
File.. file:/i:/.maven/plugins/maven-multiproject-plugin-1.0-SNAPSHOT/
Element... maven:reactor
Line.. 42
Column 7
Unable to obtain goal [site] -- file:/i:/.maven/plugins/maven-site-plugin-1.3/:2
2:42: attainGoal Goal [xdoc:register-reports] has no action definition.

Any help on why the error may be happening and how to solve it is appreciated.

Thanks,

Shawn Dahlen

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



Problem with convert-snapshot goal

2003-10-15 Thread Christian Goos
Hi,

I was trying to use the convert-snapshot goals of the release plugin.
However the plugin did not replace the Snapshot versions.
I had a look in the source code and when I replaced the getVariables.
section in the call to getFile of org.apache.maven.util.HttpUtils with some
hardcoded strings it is working correctly. What might be the problem with
that.

Thanks for help
Christian


..
getFile( url,
snapshotVersionFile,
true, // ignore errors
false, // use timestamps
(String) getVariables().get( MavenConstants.PROXY_HOST ), // works when set
to string literal
(String) getVariables().get( MavenConstants.PROXY_PORT ), // works when set
to string literal
..

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



Re: jcoverage plugin

2003-10-15 Thread Gilles Dodinet
Dominik,

Thanks for your reply. It sure helped me a lot to find the root of the 
problem. It was caused by the eclipse project configuration which didnt 
allow multiple output folders, thus writing test classes to 
target/classes and besides, my custom cleaning goal didnt specify 
clean:clean as a prereq. everything is working correctly now.. thanks.

-- gd

Dominik Dahlem wrote:

Hi,

all classes in ${maven.build.dest} are instrumented. I'm not using any
properties to run jcoverage.
Maybe your test classes compile to ${maven.build.dest} as well.
Dominik



On Wed, 2003-10-15 at 00:26, Gilles Dodinet wrote:
 

Hi-

I am not familiar with the jcoverage tool and i have some trouble with 
the maven jcoverage plugin. The problem is that all classes are reported 
in the coverage plugin, including test classes, thus the package 
statistics are biased. I think i have missed some useful properties, 
which ones tho ? i am, e.g.,. not sure of what the 
maven.jcoverage.merge.instrumentedFiles property is used for. Any hint ?

thanks for your help.

-- gd

-
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: runtime inspection of release info

2003-10-15 Thread Marc Portier
Sonnek,

worked here immediately
I did make sure I was running the class from the jar (and not from 
target/classes in the classpath)

afraid I haven't got more ideas here and now..
-marc=
Sonnek, Ryan wrote:

Sorry about the OT question, but how did you extract the
implementation-version info?  Running in winxp, suns' sdk 1.4.2, I get null
whenever I try to get the info.  Maven built the manifest correctly, but my
app can't get the info.  Here's what I've tried:
//these two give me null for the implementation version
MyClass.class.getPackage().getImplementationVersion();
this.getClass().getPackage().getImplementationVersion();
//this gives me a NPE on the getPackage() call.
Package.getPackage(maven version info).getImplementationVersion();
I've gone through several forums enteries, but haven't got code working so
far.  Appreciate any help or direction!
Ryan

-Original Message-
From: Marc Portier [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 15, 2003 6:37 AM
To: Maven Users List
Subject: Re: runtime inspection of release info

wow, thx Mike, was indeed what I was looking for.
looks like another one of the well kept secrets of java.lang.* :-)
-marc=

Mike Gilbert wrote:


Hi Marc,

have a look at

http://java.sun.com/products/jdk/1.2/docs/guide/versioning/spec/VersioningSp

ecification.html#PackageVersioning

and

http://java.sun.com/j2se/1.4.1/docs/api/java/lang/Package.html




-Original Message-
From: Marc Portier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 8:04 AM
To: 'Maven Users List'
Subject: runtime inspection of release info
Hi all,

I want to achieve the following:
- have an easy mechanism for applications to be able to inspect their
own release information at runtime... (think about:
help/about dialogs
or log statements showing some release info)
(the info to gather would be the kind of stuf inside the
manifest.mf file)
I was thinking of the following approach:
- generate just before compilation a class
myproject.package.ReleaseInfo
that holds the info hardcoded
before delving into it deaper I was hoping one of you could tell me:
1/ it's already done (couldn't find it)
2/ euh, a number of reasons not to get to do it ;-)
3/ sensible suggestions towards just doing it
regards and thx
-marc=
--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java  XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.525 / Virus Database: 322 - Release Date: 09/10/2003


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.525 / Virus Database: 322 - Release Date: 09/10/2003


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


--
Marc Portierhttp://outerthought.org/
Outerthought - Open Source, Java  XML Competence Support Center
Read my weblog at  http://radio.weblogs.com/0116284/
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Exploded EAR How-To

2003-10-15 Thread Bryce Fischer
I'm looking through the plugins now to see the best way to do this.

I've got 2 ejb-jars, 1 war combined into 1 ear file into JBoss.

I'm getting ready to do some maintenance, so naturally, deploying all
that every time can be time consuming.

What I'm wanting to do is deploy an exploded ear file, with the rest
exploded as well. That way, I only have to deploy changed files.

Any recommendations? Examples?

TIA

-- 
Bryce Fischer [EMAIL PROTECTED]


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



Re: How to fail inside a maven plugin

2003-10-15 Thread dion
Why not use the paramCheck tag?

http://maven.apache.org/tags.html#maven:paramCheck
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/


[EMAIL PROTECTED] wrote on 16/10/2003 12:03:46 AM:

 Hi there,
 
 How to fail inside a maven plugin ?
 
 example:
 
  goal name=init
 
 j:set var=errorfalse/j:set
 j:if test=${class.dir == null}
ant:echo message=property 'class.dir' not present/
 j:set var=errortrue/j:set
   /j:if
   j:if test=${error == 'true'}
  ant:echo message=Missing properties !/
  FAIL HERE
   /j:if
  ...
  /goal
 
 Thx,
 -emmanuel
 
 -
 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: Problem with convert-snapshot goal

2003-10-15 Thread dion
Version of Maven/plugin?
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/


Christian Goos [EMAIL PROTECTED] wrote on 16/10/2003 
03:34:16 AM:

 Hi,
 
 I was trying to use the convert-snapshot goals of the release plugin.
 However the plugin did not replace the Snapshot versions.
 I had a look in the source code and when I replaced the 
getVariables.
 section in the call to getFile of org.apache.maven.util.HttpUtils with 
some
 hardcoded strings it is working correctly. What might be the problem 
with
 that.
 
 Thanks for help
 Christian
 
 
 ..
 getFile( url,
 snapshotVersionFile,
 true, // ignore errors
 false, // use timestamps
 (String) getVariables().get( MavenConstants.PROXY_HOST ), // works when 
set
 to string literal
 (String) getVariables().get( MavenConstants.PROXY_PORT ), // works when 
set
 to string literal
 ..
 
 -
 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: Multiproject

2003-10-15 Thread dion
Can you provide some more information?

What goal(s) are you running?
What are your multiproject properties set to?
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/


Dahlen Jr, Shawn M [EMAIL PROTECTED] wrote on 16/10/2003 
02:58:21 AM:

 Hello -
 
 I'm attempting to use the multiproject plugin to generate a website 
 and I continually recieve
 the following error:
 
 BUILD FAILED
 File.. 
file:/i:/.maven/plugins/maven-multiproject-plugin-1.0-SNAPSHOT/
 Element... maven:reactor
 Line.. 42
 Column 7
 Unable to obtain goal [site] -- file:/i:/.maven/plugins/maven-site-
 plugin-1.3/:2
 2:42: attainGoal Goal [xdoc:register-reports] has no action 
definition.
 
 Any help on why the error may be happening and how to solve it is 
appreciated.
 
 Thanks,
 
 Shawn Dahlen
 
 -
 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]



jalopy format

2003-10-15 Thread Nathan Coast
Hi,

Apologies as this is jalopy question but the jalopy mailing list has zero trafic.

I'd like this format for wrapped method parameters

public EJBLocalHome getLocalHome(String jndiName,
 Class homeClass,
 String mung,
 String foo)
{
but when I set paramsMethodDeftrue/paramsMethodDef, I get this:

public static final EJBLocalHome getLocalHome(
String jndiName,
Class homeClass,
String mung,
String foo)
{
anyone have any ideas what needs setting to get what I want?  I've tried 
numerous configurations but none seem to do what I want.

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