RE: [multiproject] Strange...

2004-03-30 Thread Jörg Schaible
Niclas Hedhman wrote on Tuesday, March 30, 2004 9:39 AM:

 On Tuesday 30 March 2004 14:49, Jörg Schaible wrote:
 Hi Niclas,
 
 avalon-excalibur/buildsystem/project-common.xml
 

 should be project.properties ?
 
 Nope...
 I was assuming that all the Organization, Mailinglists, build and
 other common stuff could be stuffed into a shared pom file. No?
 
 Documentation says;
 quote
 Values from the parent project will be the default for this project
 if they are left unspecified.
 /quote

Since this behaviour changed multiple from RC1 to RC2 it is hard to say. I would also 
believe the docs. As long as something is compiled and e.g. the developers are listed 
i nthe project members - good.

 Personally I have added a pregoal for build:start to my maven.xml's
 that will load global properties. But even here: It is too late for
 the maven.repo.remote entry. This one cannot be shared, since
 the goal runs too late.
 
 So, you are saying that the global project.properties in
 the top-level dir
 (where maven multiproject is invoked) will not be read?

Yes. This is definatly true.

 - your child project.properties should contain an entry
 maven.multiproject.type. Otherwise multiproject does not know, what
 to call. Maybe this is your problem below ?
 
 Docs says that jar is default type (although the Optional=No).

ok then.

 - maven.javadoc.stylesheet
 =file:${avalon.buildsystem}/stylesheet.css
 will not work. All you define here is the link that is inserted in
 your HTML code. There are open JIRA issues (with patch) to solve
 this, but they're not applied
 
 I worry about this later.

:)
 
 Try to validate your POMs with pom:validate.
 
 Is the POM xml 'order sensitive', or just the pom:validate?

Just the pom:validate, since the POM is not validated for execution (too expensive). 
But this means maven will just use what if finds and you'll never know if something is 
ignored. Guess, I had once a dependemcy tag and wondered why ... ;-)

But nothing of this should create your original problem. Did you run maven with -X 
option ?

 Point in hand; I want a default Maven project with heaps of
 subprojects without hordes of maven.xml coding, in fact I don't want
 any maven.xml at all. Is this possible or not?  If so, what is the
 expected project layout? 

Well, you can omit the maven.xml, if you don't use global properties. But then you 
have to repeat them in any of the subprojects also. Additionally you cannot have a 
global theme.css, this must also live in each subproject. Solving this problems 
results again in a maven.xml in each subproject ... I do not know what is really 
better ...

Regards,
Jörg

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



Re: [multiproject] Strange...

2004-03-30 Thread Niclas Hedhman

Solved (thanks to Stephen McConnell)!

maven.license.licenseFile had a file:, which it couldn't

Probably same for other locations. Could there be some unfied way of how files 
and directories are indicated. It will be impossible to remember when to use 
file:// URLs and when not.

My suggestion is that file: is NEVER used/required, and where URLs are 
allowed/required, the code adds file: intelligently.

Cheers
Niclas

-- 
+-//---+
|   http://www.bali.ac |
|  http://niclas.hedhman.org   |
+--//--+

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



RE: [multiproject] Strange...

2004-03-29 Thread Brett Porter
This is purely a hunch, but I've seen sections of the Avalon build that uses
ant properties to set things for Jelly to use which could potentially cause
this. Because ant properties behave differently to jelly (ie first wins
instead of last wins), this can break in certain situations - and changes
somewhere in the late betas did just that.

Did it work with different versions of Maven?

- Brett

 -Original Message-
 From: Niclas Hedhman [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, 30 March 2004 3:36 PM
 To: [EMAIL PROTECTED]
 Subject: [multiproject] Strange...
 
 
 
 Hi,
 
 I am getting the following strange exception when running 
 multiproject:install 
 on RC2
 
 BUILD FAILED
 File.. 
 file:/home/niclas/.maven/plugins/maven-multiproject-plugin-1.2
/plugin.jelly
Element... maven:reactor
Line.. 202
Column 9
Unable to obtain goal [multiproject:install-callback] -- 
file:/home/niclas/.maven/plugins/maven-jar-plugin-1.4/plugin.jelly:32:40: 
ant:jar 
/home/niclas/dev/opensource/avalon-excalibur/file:/home/niclas/dev/opensourc
e/avalon-excalibur/compatibility 
not found.
Total time: 28 seconds
Finished at: Tue Mar 30 13:29:05 MYT 2004


'compatibility' is the subproject name.

Somehow, the /home/niclas/dev/opensource/avalon-excalibur/  top-level 
directory is added in front of the 
file:/home/niclas/dev/opensource/avalon-excalibur/compatibility
sub-project 
dir.


Any clues what I have missed?

Niclas
-- 
+-//---+
|   http://www.bali.ac |
|  http://niclas.hedhman.org   |
+--//--+

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


Re: [multiproject] Strange...

2004-03-29 Thread Niclas Hedhman
On Tuesday 30 March 2004 13:45, Brett Porter wrote:
 This is purely a hunch, but I've seen sections of the Avalon build that
 uses ant properties to set things for Jelly to use which could potentially
 cause this. Because ant properties behave differently to jelly (ie first
 wins instead of last wins), this can break in certain situations - and
 changes somewhere in the late betas did just that.

 Did it work with different versions of Maven?

That I don't know.
I am restructuring the whole Avalon Excalibur, so that all the 'home made' 
maven.xml can be removed and build all the systems with a single command.

Yesterday, I had it running (with RC2), and have since then modified the 
'inheritence', ripped away tons of properties and maven.xml stuff, now down 
to nearly nothing.

This is the 'first' subproject without any dependencies, so I assume it is 
something with 'common stuff'.

Attached are;
avalon-excalibur/buildsystem/project-common.xml
avalon-excalibur/project-common.xml
avalon-excalibur/compatibility/project.xml
avalon-excalibur/compatibility/project.properties

No maven.xml involved at all !!

Any help is very much appreciated !

Niclas
-- 
+-//---+
|   http://www.bali.ac |
|  http://niclas.hedhman.org   |
+--//--+
maven.repo.remote = 
http://www.apache.org/dist/avalon,http://www.ibiblio.org/maven,http://lsd.student.utwente.nl/repository

maven.docs.src=${basedir}/site/xdocs
maven.docs.outputencoding=UTF-8

#
# Banner background and foreground colors.
#

maven.ui.banner.background = #fff
maven.ui.banner.foreground = #000
maven.xdoc.jsl = file:${avalon.buildsysten}/site.jsl
maven.javadoc.stylesheet =file:${avalon.buildsystem}/stylesheet.css
maven.javadoc.links = 
${sun.j2se.link},${avalon.logkit.link},${avalon.framework.link},${excalibur.thread.link},${excalibur.event.link}
maven.license.licenseFile = file:${basedir}/LICENSE.txt
maven.xdoc.poweredby.image=

#
# Declaration of the remote links to assign on javadoc generation.
# Link declarations can be overriden in the user's build.properties
# file.
#

sun.j2se.link = http://java.sun.com/j2se/1.4/docs/api/
avalon.framework.link = http://avalon.apache.org/framework/api/
avalon.logkit.link = http://avalon.apache.org/logkit/api/
excalibur.thread.link = http://avalon.apache.org/excalibur/thread/api/
excalibur.event.link = http://avalon.apache.org/excalibur/event/api/

maven.multiproject.includes=**/project.xml
?xml version=1.0 encoding=ISO-8859-1?

project
  pomVersion3/pomVersion
  nameAvalon Legacy - Excalibur/name
  organization
nameThe Apache Software Foundation/name
urlhttp://avalon.apache.org//url
logohttp://avalon.apache.org/images/apache-avalon-logo.png/logo
  /organization
  inceptionYear1997/inceptionYear

  licenses
license
  nameApache Software License 1.1/name
  distributionrepo/distribution
  urlhttp://www.apache.org/LICENSE.txt/url
/license
  /licenses

  packageorg.apache.avalon/package
  gumpRepositoryIdavalon-excalibur/gumpRepositoryId

  urlhttp://avalon.apache.org/excalibur//url
  issueTrackingUrlhttp://nagoya.apache.org//issueTrackingUrl

  siteAddressavalon.apache.org/siteAddress
  siteDirectory${root.site.directory}/excalibur/siteDirectory
  distributionDirectory/distributionDirectory

  repository
connectionscm:cvs:pserver:[EMAIL PROTECTED]:/home/cvspublic:avalon-excalibur/connection
urlhttp://cvs.apache.org/viewcvs/avalon-excalibur//url
  /repository

  mailingLists
mailingList
  nameAvalon Developer List/name
  subscribe[EMAIL PROTECTED]/subscribe
  unsubscribe[EMAIL PROTECTED]/unsubscribe
  archivehttp://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]/archive
/mailingList
mailingList
  nameAvalon User List/name
  subscribe[EMAIL PROTECTED]/subscribe
  unsubscribe[EMAIL PROTECTED]/unsubscribe
  archivehttp://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]/archive
/mailingList
  /mailingLists

  developers
developer
  namePaul Hammant/name
  email[EMAIL PROTECTED]/email
  idhammant/id
/developer
developer
  nameBerin Loritsch/name
  idbloritsch/id
  email[EMAIL PROTECTED]/email
/developer
developer
  nameStephen McConnell/name
  idmcconnell/id
  email[EMAIL PROTECTED]/email
/developer
developer
  nameLeo Simons/name
  idleosimons/id
  email[EMAIL PROTECTED]/email
/developer
developer
  nameJeff Turner/name
  idjefft/id
  email[EMAIL PROTECTED]/email
/developer
developer
  nameCostin Manolache/name
/developer
developer
  nameCraig McClanahan/name
/developer
developer
  nameEung-ju Park/name
  idcolus/id
  email[EMAIL PROTECTED]/email
/developer
developer
  nameFederico Barbieri/name
  idfede/id
  email[EMAIL PROTECTED]/email
/developer
developer
  nameLeif Mortenson/name
  idfede/id
  email[EMAIL