Hmmm, Maven could be extended to accommodate this style, by writing more
Maven code, so it is not technically an issue in theory.
From a visibility of what is there perspective though, I think that
module names that clearly identified that there are API and IMPL
components would make the intent clearer. At the moment, one has to
deduce from the existence of the pom files that this is so, or read
something else.
Changing to a structure that had module names as *api/impl would be self
documenting, so I think it would be a good idea to make this change anyway.
Regards
Nathan
Daniel Jemiolo wrote:
The API and implementation code is split so that users can provide
alternate implementations of WS-* capabilities without dragging in unused
code from Muse. I put the API/impl code under the same module because it
seemed natural to me, but it can be changed. Assuming it's really hard to
make Maven2 deal with multiple POMs (I guess there's no XML equivalent of
the -f flag?), I can move the ws*-api and ws*-impl modules right below
/trunk.
Dan
Nathan Sowatskey <[EMAIL PROTECTED]> wrote on 07/12/2006 10:38:25 AM:
Sure I can do that, though it won't actually work until we address my
question about the nature of the pom-api and pom-impl files in the
modules.
Does anyone know why that was done that way?
Many thanks
Nathan
Daniel Jemiolo wrote:
Hi Nathan,
This is great! I tried to figure out how to do this with Maven2
initially
but couldn't figure it out - I did not get from the sample XML that
"modules" could also mean "projects", and the only mailing list talk I
could find recommended the approach we have now. Can you please open
an
issue in JIRA and then attach your POM file, just so the contribution
is
logged (along with the licensing checkbox)? I can then add it to the
build.
Thanks!
Dan
Nathan Sowatskey <[EMAIL PROTECTED]> wrote on 07/12/2006 04:03:40 AM:
Hi
The first cut of the top level pom.xml is attached, which should be
placed in the trunk dir containing the modules dir.
This doesn't work as is, because of the way that the modules have
defined their pom files, using pom-api and pom-impl.
Whilst the technique used works using the batch file, it doesn't
reflect
the common usage of modules for nested Maven 2.x projects. What one
would expect to see is a single pom.xml for each of the modules. That
would allow the build from the top level trunk dir to iterate over
the
listed modules, invoking maven on each of the pom files in the nested
projects.
This is all, obviously, fixable, but before I go about changing what
has
already been done, I'd like to have some sense of what the raison
d'etre
is for the current approach.
So, thoughts anyone?
Many thanks
Nathan
Hawkins, Joel wrote:
+1 on the maven suggestions! :-)
Joel
-----Original Message-----
From: Daniel Jemiolo [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 11, 2006 12:02 PM
To: [email protected]
Cc: [email protected]; [email protected]
Subject: Re: Building Muse
Hi,
We're currently using Maven 2.0 - if you install that (including the
initial run where it gathers all of the dependencies), you can then
run
build-all.bat from /trunk to install the JARs in your local
repository.
The root directory for the Muse JARS in your repository will be
/muse.
Thanks,
Dan
P.S. Any Maven help, suggestions, etc., would be appreciated! We're
all
fairly new to it.
Nathan Sowatskey <[EMAIL PROTECTED]> wrote on 07/11/2006 09:29:44
AM:
Hi
I am just getting to grips with Muse. I have the svn repository
locally,
and I am trying to build it.
The build instructions at the top level, trunk, seem to imply that
Maven
1.x is required to build, though there are no build files in that
directory.
The modules have pom.xml files, and the build.bat looks like it is
using
Maven 2.x.
I can appreciate that maybe we are just in the middle of moving
from
one
to the other. I know Maven, so I may be able to help if anyone
wants
to
give me some pointers.
Regards
Nathan
--
Nathan Sowatskey - Technical Leader, NMTG CTO Engineering - Desk
+34-91-201-2139 - Mobile +34-638-083-675 - AIM id NathanCisco -
[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]
The contents of this e-mail are intended for the named addressee
only.
It
contains information that may be confidential. Unless you are the
named
addressee or an authorized designee, you may not copy or use it, or
disclose
it to anyone else. If you received it in error please notify us
immediately
and then destroy it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Nathan Sowatskey - Technical Leader, NMTG CTO Engineering - Desk
+34-91-201-2139 - Mobile +34-638-083-675 - AIM id NathanCisco -
[EMAIL PROTECTED]
<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.
org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.
org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>ws.apache.muse</groupId>
<artifactId>muse</artifactId>
<version>2.0-SNAPSHOT</version>
<name>Apache MUSE - Web Services Distributed Management (WSDM)
implementation</name>
<description>
<![CDATA[
This project addresses the work required to produce an open
source
implementation of WSDM (http://www.oasis-open.org/committees/wsdm).
]]>
</description>
<url>http://ws.apache.org/muse/</url>
<packaging>pom</packaging>
<organization>
<name>Apache Web Services - Muse</name>
<url>http://ws.apache.org/muse/</url>
</organization>
<modules>
<module>modules/muse-core</module>
<module>modules/muse-platform-axis2</module>
<module>modules/muse-tools</module>
<module>modules/muse-util</module>
<module>modules/muse-util-qname</module>
<module>modules/muse-util-xml</module>
<module>modules/muse-util-xstream</module>
<module>modules/muse-wsa-soap</module>
<module>modules/muse-wsdm-muws</module>
<module>modules/muse-wsdm-muws-adv</module>
<module>modules/muse-wsdm-wef</module>
<module>modules/muse-wsn</module>
<module>modules/muse-wsrf</module>
<module>modules/muse-wsx</module>
</modules>
<inceptionYear>2005</inceptionYear>
<scm>
<connection>scm:svn:http://svn.apache.org/repos/asf/webservices/muse</connection>
<developerConnection>scm:svn:https://svn.apache.
org/repos/asf/webservices/muse</developerConnection>
<url>http://svn.apache.org/repos/asf/webservices/muse</url>
</scm>
<issueManagement>
<system>jira</system>
<url>http://issues.apache.org/jira/browse/MUSE-30</url>
</issueManagement>
<mailingLists>
<mailingList>
<name>Muse User List</name>
<subscribe>[EMAIL PROTECTED]</subscribe>
<unsubscribe>[EMAIL PROTECTED]</unsubscribe>
<post>[email protected]</post>
<archive>http://ws.apache.org/mail/muse-user/</archive>
</mailingList>
<mailingList>
<name>Muse Developer List</name>
<subscribe>[EMAIL PROTECTED]</subscribe>
<unsubscribe>[EMAIL PROTECTED]</unsubscribe>
<post>[email protected]</post>
<archive>http://ws.apache.org/mail/muse-dev/</archive>
</mailingList>
<mailingList>
<name>Muse Commits List</name>
<subscribe>[EMAIL PROTECTED]</subscribe>
<unsubscribe>[EMAIL PROTECTED]</unsubscribe>
<post>[email protected]</post>
<archive>http://ws.apache.org/mail/muse-commits/</archive>
</mailingList>
</mailingLists>
<build>
<defaultGoal>install</defaultGoal>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<configuration>
<locales>en</locales>
<templateDirectory>file:src/site/resources/</templateDirectory>
<template>maven-site.vm</template>
</configuration>
</plugin>
</plugins>
</build>
<licenses>
<license>
<name>Apache Licence</name>
<url>http://www.apache.org/licenses/</url>
<distribution>repo</distribution>
</license>
</licenses>
</project>
---------------------------------------------------------------------
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]
--
Nathan Sowatskey - Technical Leader, NMTG CTO Engineering - Desk
+34-91-201-2139 - Mobile +34-638-083-675 - AIM id NathanCisco -
[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]
--
Nathan Sowatskey - Technical Leader, NMTG CTO Engineering - Desk
+34-91-201-2139 - Mobile +34-638-083-675 - AIM id NathanCisco -
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
