Mailing-List: contact commons-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: commons-dev@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of andreas.veithen@skynet.be
 designates 195.238.6.179 as permitted sender)
Message-ID: <48EB1F89.8020906@skynet.be>
Date: Tue, 07 Oct 2008 10:36:25 +0200
From: Andreas Veithen <andreas.veithen@skynet.be>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: commons-dev@ws.apache.org
Subject: Re: [Transport] Parent module of transports removed
References: <672a01200810070104j302a076fme4323eb009d4c73b@mail.gmail.com>
In-Reply-To: <672a01200810070104j302a076fme4323eb009d4c73b@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

As the name implies the parent POM is the parent of all other modules 
(except the POM in the root directory), so it's not at all obsolete and 
you should not remove it. If you are still able to build the transports 
after removing this, it is only because this parent POM is still 
available from your local (or some other) repository! Can you please 
revert this?

Andreas

Ruwan Linton wrote:
> Hi devs,
>
> I had a look at the current maven build of the transports and realized that
> the complete axis2-transports.jar is generated from the root pom but there
> is an obsolete module also to do the same but is not doing anything.
> Therefore I removed that. Andreas, I hope this ok from the tests reports
> point of view as well.
>
> At the same time for the moment this complete transports jar is generated
> with out the jar plugin and we will need to change the way we build this jar
> in order to produce an OSGi bundle jar (but not just a jar). Hope it is OK.
>
> Thanks,
> Ruwan
>
>