You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by Ruwan Linton <ru...@gmail.com> on 2008/10/07 10:04:43 UTC
[Transport] Parent module of transports removed
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
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Transport] Parent module of transports removed
Posted by Ruwan Linton <ru...@gmail.com>.
Hi Deepal,
I read the readme but, since the parent pom was on my local repo, it was
building for me :(.
I think we should be able to get rid of this parent module. I will try to
come up with a solution, if at all possible...
Thanks,
Ruwan
On Tue, Oct 7, 2008 at 5:19 PM, Deepal jayasinghe <de...@gmail.com> wrote:
> 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.
> >
> Nope its not ok. Did you ever read the readme.txt ?
> The main reason I added that to build a complete transport jar. If you
> know any other way to do that please go ahead and remove that. Please
> remember we need to build a complete jar including all the transports.
> > 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.
> >
> If you get the complete jar working I have no problem. Because I came up
> with that solution after spending a day (I know my knowledge on maven is
> very little).
>
> -Deepal
> > Thanks,
> > Ruwan
> >
> >
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Transport] Parent module of transports removed
Posted by Deepal jayasinghe <de...@gmail.com>.
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.
>
Nope its not ok. Did you ever read the readme.txt ?
The main reason I added that to build a complete transport jar. If you
know any other way to do that please go ahead and remove that. Please
remember we need to build a complete jar including all the transports.
> 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.
>
If you get the complete jar working I have no problem. Because I came up
with that solution after spending a day (I know my knowledge on maven is
very little).
-Deepal
> Thanks,
> Ruwan
>
>
--
Thank you!
http://blogs.deepal.org
Re: [Transport] Parent module of transports removed
Posted by Andreas Veithen <an...@skynet.be>.
[Reposting since my first message didn't make it to the list]
Ruwan,
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
>
>
Re: [Transport] Parent module of transports removed
Posted by Ruwan Linton <ru...@gmail.com>.
Andreas,
I agree we need to move these meta data to the root pom as well. At the same
time I have a suggestion to do this, which is to get a copy of the sources
from all the modules to a tem directory using an ant task and use the bundle
plugin to generate the artifact.
I will have a look at maven-shade-plugin as well.
Thanks,
Ruwan
On Wed, Oct 8, 2008 at 2:39 AM, Andreas Veithen
<an...@skynet.be>wrote:
> Ruwan,
>
> If we can eliminate the parent module in a clean way, I'm in favor of it.
> In the meantime, I restored it so that the code can be built correctly.
> Please also note that the parent POM contains some metadata (mailing lists,
> dev team, etc.) that should be moved to the axis2-transports POM before we
> remove the parent module.
>
> I noticed that the Geronimo project uses maven-shade-plugin to build the
> kind of uber-JAR we are looking for. Maybe this works better with OSGi?
>
> Andreas
>
>
>
> On 7 oct. 08, at 17:33, Ruwan Linton wrote:
>
> Hhhhmmmm :( I am sorry, you are correct it was building for me because it
>> is
>> on my local maven repo.
>>
>> I saw you have reverted the parent module, but I still think we should be
>> able to get rid of this and make the root pom as the parent pom.
>>
>> Any way the current strategy of building the complete jar is not gonna
>> work
>> for the OSGi bundle generation. I will have a look at this and get back.
>>
>> Thanks,
>> Ruwan
>>
>> On Tue, Oct 7, 2008 at 2:06 PM, Andreas Veithen
>> <an...@skynet.be>wrote:
>>
>> 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
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>> --
>> Ruwan Linton
>> http://wso2.org - "Oxygenating the Web Services Platform"
>> http://ruwansblog.blogspot.com/
>>
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Transport] Parent module of transports removed
Posted by Andreas Veithen <an...@skynet.be>.
Ruwan,
If we can eliminate the parent module in a clean way, I'm in favor of
it. In the meantime, I restored it so that the code can be built
correctly. Please also note that the parent POM contains some metadata
(mailing lists, dev team, etc.) that should be moved to the axis2-
transports POM before we remove the parent module.
I noticed that the Geronimo project uses maven-shade-plugin to build
the kind of uber-JAR we are looking for. Maybe this works better with
OSGi?
Andreas
On 7 oct. 08, at 17:33, Ruwan Linton wrote:
> Hhhhmmmm :( I am sorry, you are correct it was building for me
> because it is
> on my local maven repo.
>
> I saw you have reverted the parent module, but I still think we
> should be
> able to get rid of this and make the root pom as the parent pom.
>
> Any way the current strategy of building the complete jar is not
> gonna work
> for the OSGi bundle generation. I will have a look at this and get
> back.
>
> Thanks,
> Ruwan
>
> On Tue, Oct 7, 2008 at 2:06 PM, Andreas Veithen
> <an...@skynet.be>wrote:
>
>> 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
>>>
>>>
>>>
>>
>>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
Re: [Transport] Parent module of transports removed
Posted by Deepal jayasinghe <de...@gmail.com>.
Ruwan Linton wrote:
> Hhhhmmmm :( I am sorry, you are correct it was building for me because it is
> on my local maven repo.
>
> I saw you have reverted the parent module, but I still think we should be
> able to get rid of this and make the root pom as the parent pom.
>
Believe me I also had the same impression , however I spent a day but no
successes. So I created that parent module and pom.xml
-Deepal
> Any way the current strategy of building the complete jar is not gonna work
> for the OSGi bundle generation. I will have a look at this and get back.
>
> Thanks,
> Ruwan
>
> On Tue, Oct 7, 2008 at 2:06 PM, Andreas Veithen
> <an...@skynet.be>wrote:
>
>
>> 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
>>>
>>>
>>>
>>>
>>
>
>
>
--
Thank you!
http://blogs.deepal.org
Re: [Transport] Parent module of transports removed
Posted by Ruwan Linton <ru...@gmail.com>.
Hhhhmmmm :( I am sorry, you are correct it was building for me because it is
on my local maven repo.
I saw you have reverted the parent module, but I still think we should be
able to get rid of this and make the root pom as the parent pom.
Any way the current strategy of building the complete jar is not gonna work
for the OSGi bundle generation. I will have a look at this and get back.
Thanks,
Ruwan
On Tue, Oct 7, 2008 at 2:06 PM, Andreas Veithen
<an...@skynet.be>wrote:
> 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
>>
>>
>>
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Transport] Parent module of transports removed
Posted by Andreas Veithen <an...@skynet.be>.
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
>
>