Home » Eclipse Projects » Orbit » Jakarta Commons / Net
| Jakarta Commons / Net [message #2880] |
Tue, 11 July 2006 07:47  |
 Martin Oberhuber
Messages: 1007
Registered: July 2009 |
Senior Member |
|
|
Hi,
just FYI, the DSDP Target Management Project is planning to bring the
Jakarta Commons/Net library to Eclipse. We have already initiated the
EMO review process in May, and since the Apache license is deemed
compatible, we hope that to complete soon.
We'll be happy to have Jakarta Commons/Net live in the Orbit project
instead of ur own, if others are interested too.
Jakarta Commons/Net brings well-established implementations for Telnet,
FTP, rlogin / rcp and other basic protocols, and Ant tasks for using
these protocols are already part of Eclipse so a drop-in of commons/net
would immediately give more power to Ant too.
--
Thanks,
Martin Oberhuber
Target Management Project Lead.
|
|
|
| Re: Jakarta Commons / Net [message #2953 is a reply to message #2880] |
Tue, 11 July 2006 12:09  |
Eclipse User |
|
|
|
Originally posted by: grahame.jivamedical.com
Martin Oberhuber wrote:
> Hi,
>
> just FYI, the DSDP Target Management Project is planning to bring the
> Jakarta Commons/Net library to Eclipse. We have already initiated the
> EMO review process in May, and since the Apache license is deemed
> compatible, we hope that to complete soon.
do we have to go through the legal process for Apache code? I didn't
think that we do?
> We'll be happy to have Jakarta Commons/Net live in the Orbit project
> instead of ur own, if others are interested too.
Orbit should bring all of Jakarta commons across - different projects
use different parts of it, so I'm not sure what the right packaging
solution is.
Grahame
|
|
|
| Re: Jakarta Commons / Net [message #3001 is a reply to message #2953] |
Tue, 11 July 2006 17:29 |
| Eclipse User |
|
|
|
Originally posted by: stepper.sympedia.de
Grahame,
I think a plugin per jar is mandatory.
To make them available via Update Manager it would be neccessary to
provide a feature per plugin.
In addition features for larger logical groups of features could be
provided.
Cheers
/Eike
Grahame Grieve schrieb:
> Martin Oberhuber wrote:
>> Hi,
>>
>> just FYI, the DSDP Target Management Project is planning to bring the
>> Jakarta Commons/Net library to Eclipse. We have already initiated the
>> EMO review process in May, and since the Apache license is deemed
>> compatible, we hope that to complete soon.
>
> do we have to go through the legal process for Apache code? I didn't
> think that we do?
>
>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>> instead of ur own, if others are interested too.
>
> Orbit should bring all of Jakarta commons across - different projects
> use different parts of it, so I'm not sure what the right packaging
> solution is.
>
> Grahame
|
|
|
| Re: Jakarta Commons / Net [message #3018 is a reply to message #3001] |
Tue, 11 July 2006 19:17 |
Sri Doddapaneni
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
In response to Grahame Grieve's comment:
>> do we have to go through the legal process for Apache code? I didn't
>> think that we do?
You have to go thorugh EMO legal review and approval for all thrid-party
code which includes Apache code. You may take comfort in the fact that many
of the Apache components listed are already for use in the context of TPTP
project, possibly by other projects as well. In TPTP, we have been bundling
Apache Commons Logging, Log4J and some others. For these packages, the
overhead of extending use of other Eclipse project should low on the EMO
Legal and hence possiblity of quicker turnaround.
-Sri Doddapaneni
TPTP Project
"Eike Stepper" <stepper@sympedia.de> wrote in message
news:e90n5o$gfn$1@utils.eclipse.org...
> Grahame,
>
> I think a plugin per jar is mandatory.
> To make them available via Update Manager it would be neccessary to
> provide a feature per plugin.
> In addition features for larger logical groups of features could be
> provided.
>
> Cheers
> /Eike
>
>
> Grahame Grieve schrieb:
>> Martin Oberhuber wrote:
>>> Hi,
>>>
>>> just FYI, the DSDP Target Management Project is planning to bring the
>>> Jakarta Commons/Net library to Eclipse. We have already initiated the
>>> EMO review process in May, and since the Apache license is deemed
>>> compatible, we hope that to complete soon.
>>
>> do we have to go through the legal process for Apache code? I didn't
>> think that we do?
>>
>>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>> instead of ur own, if others are interested too.
>>
>> Orbit should bring all of Jakarta commons across - different projects
>> use different parts of it, so I'm not sure what the right packaging
>> solution is.
>>
>> Grahame
|
|
|
| Re: Jakarta Commons / Net [message #3035 is a reply to message #3018] |
Tue, 11 July 2006 20:41 |
| Eclipse User |
|
|
|
Originally posted by: grahame.jivamedical.com
So, if orbit includes a package, then we wouldn't have to go through
the EMO legal review process to use it, on the basis that it's already
done?
Grahame
Sri Doddapaneni wrote:
> In response to Grahame Grieve's comment:
>>> do we have to go through the legal process for Apache code? I didn't
>>> think that we do?
>
> You have to go thorugh EMO legal review and approval for all thrid-party
> code which includes Apache code. You may take comfort in the fact that many
> of the Apache components listed are already for use in the context of TPTP
> project, possibly by other projects as well. In TPTP, we have been bundling
> Apache Commons Logging, Log4J and some others. For these packages, the
> overhead of extending use of other Eclipse project should low on the EMO
> Legal and hence possiblity of quicker turnaround.
> -Sri Doddapaneni
> TPTP Project
>
>
> "Eike Stepper" <stepper@sympedia.de> wrote in message
> news:e90n5o$gfn$1@utils.eclipse.org...
>> Grahame,
>>
>> I think a plugin per jar is mandatory.
>> To make them available via Update Manager it would be neccessary to
>> provide a feature per plugin.
>> In addition features for larger logical groups of features could be
>> provided.
>>
>> Cheers
>> /Eike
>>
>>
>> Grahame Grieve schrieb:
>>> Martin Oberhuber wrote:
>>>> Hi,
>>>>
>>>> just FYI, the DSDP Target Management Project is planning to bring the
>>>> Jakarta Commons/Net library to Eclipse. We have already initiated the
>>>> EMO review process in May, and since the Apache license is deemed
>>>> compatible, we hope that to complete soon.
>>> do we have to go through the legal process for Apache code? I didn't
>>> think that we do?
>>>
>>>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>>> instead of ur own, if others are interested too.
>>> Orbit should bring all of Jakarta commons across - different projects
>>> use different parts of it, so I'm not sure what the right packaging
>>> solution is.
>>>
>>> Grahame
>
>
|
|
|
| Re: Jakarta Commons / Net [message #4179 is a reply to message #3035] |
Wed, 12 July 2006 17:39 |
| Eclipse User |
|
|
|
Originally posted by: jeff_mcaffer.REMOVE.ca.ibm.com
Grahame Grieve wrote:
> So, if orbit includes a package, then we wouldn't have to go through
> the EMO legal review process to use it, on the basis that it's already
> done?
Orbit does NOT affect the IP policy or process in any way.
One more time cause this is really important...
Orbit does NOT affect the IP policy or process in any way.
You still have to do whatever it says you have to do (I don't want to be
the one interpreting that :-) Orbit is a repository for the *output* of
that process in the form of bundle libraries.
The IP process has been evolving to make things easier for people and
will continue to do so. Every project still needs to submit a
contribution quesitonnaire. There are some new 'features' that allow
the EMO to approve libs for use by all projects HOWEVER, you STILL have
to submit a questionaire so that the Foundation knows of your intention
to use one of these libs.
Jeff
|
|
|
| 3rd party redistribution process (was: Jakarta Commons / Net) [message #4598 is a reply to message #3018] |
Thu, 13 July 2006 07:50 |
Martin Oberhuber
Messages: 1007
Registered: July 2009 |
Senior Member |
|
|
Hello Sri,
As we are going to set up Eclipse projects as containers for
Jakarta Commons Net and ORO, I'm looking for "templates" or
other pointers that help me doing so.
I'm currently looking at the org.apache.ant project, so what
I'm planning to do is
- check in the original *.jar files,
- create and checkin *.zip files to hold the sources
(need to create new ones to factor out examples we don't
want to redistribute)
- create new wrapper .classpath and Manifest.mf files
From your experience, does this approach make sense? IMHO, one
disadvantage of this seems to be that we cannot create JAR'ed
plugins, so Webstart won't be possible. For JAR'ed plugins we'd
have to replace the Manifest.MF and add about.html to the
original *.jar, but I'd rather not touch the original binary...
Does anybody have comments on the process?
Could you point me to the places where Log4J and others are hosted
in the TPTP CVS Repository, such that I can also look at these as
a template? I'm wondering how to do the Features for the Update
Manager for instance.
Do you have any other supporting information that might help me?
Thanks,
Martin
--
Martin Oberhuber - WindRiver, Austria
+43(662)457915-85
Sri Doddapaneni wrote:
> In response to Grahame Grieve's comment:
>
>>>do we have to go through the legal process for Apache code? I didn't
>>>think that we do?
>
>
> You have to go thorugh EMO legal review and approval for all thrid-party
> code which includes Apache code. You may take comfort in the fact that many
> of the Apache components listed are already for use in the context of TPTP
> project, possibly by other projects as well. In TPTP, we have been bundling
> Apache Commons Logging, Log4J and some others. For these packages, the
> overhead of extending use of other Eclipse project should low on the EMO
> Legal and hence possiblity of quicker turnaround.
> -Sri Doddapaneni
> TPTP Project
>
>
> "Eike Stepper" <stepper@sympedia.de> wrote in message
> news:e90n5o$gfn$1@utils.eclipse.org...
>
>>Grahame,
>>
>>I think a plugin per jar is mandatory.
>>To make them available via Update Manager it would be neccessary to
>>provide a feature per plugin.
>>In addition features for larger logical groups of features could be
>>provided.
>>
>>Cheers
>>/Eike
>>
>>
>>Grahame Grieve schrieb:
>>
>>>Martin Oberhuber wrote:
>>>
>>>>Hi,
>>>>
>>>>just FYI, the DSDP Target Management Project is planning to bring the
>>>>Jakarta Commons/Net library to Eclipse. We have already initiated the
>>>>EMO review process in May, and since the Apache license is deemed
>>>>compatible, we hope that to complete soon.
>>>
>>>do we have to go through the legal process for Apache code? I didn't
>>>think that we do?
>>>
>>>
>>>>We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>>>instead of ur own, if others are interested too.
>>>
>>>Orbit should bring all of Jakarta commons across - different projects
>>>use different parts of it, so I'm not sure what the right packaging
>>>solution is.
>>>
>>>Grahame
>
>
>
|
|
|
| Re: Jakarta Commons / Net [message #4670 is a reply to message #3001] |
Thu, 13 July 2006 07:54 |
Martin Oberhuber
Messages: 1007
Registered: July 2009 |
Senior Member |
|
|
Hello Eike,
In order to provide sources, even more is needed for each jar:
- One plugin for the binaries
- One feature for the binary-plugin in update manager
- Another plugin holding the sources
- One feature for the sources in update manager
For the source feature I'm not sure, perhaps sources for multiple
jar's could be packaged into a single source feature? - Perhaps
that could be another advantage of collecting 3rd party libs in
the Orbit project, it allows a build process to collect sources
into a single source feature for update manager.
Cheers,
Martin
--
Martin Oberhuber - WindRiver, Austria
+43(662)457915-85
Eike Stepper wrote:
> Grahame,
>
> I think a plugin per jar is mandatory.
> To make them available via Update Manager it would be neccessary to
> provide a feature per plugin.
> In addition features for larger logical groups of features could be
> provided.
>
> Cheers
> /Eike
>
>
> Grahame Grieve schrieb:
>
>> Martin Oberhuber wrote:
>>
>>> Hi,
>>>
>>> just FYI, the DSDP Target Management Project is planning to bring the
>>> Jakarta Commons/Net library to Eclipse. We have already initiated the
>>> EMO review process in May, and since the Apache license is deemed
>>> compatible, we hope that to complete soon.
>>
>>
>> do we have to go through the legal process for Apache code? I didn't
>> think that we do?
>>
>>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>> instead of ur own, if others are interested too.
>>
>>
>> Orbit should bring all of Jakarta commons across - different projects
>> use different parts of it, so I'm not sure what the right packaging
>> solution is.
>>
>> Grahame
|
|
|
| Re: Jakarta Commons / Net [message #4739 is a reply to message #4670] |
Thu, 13 July 2006 08:53 |
| Eclipse User |
|
|
|
Originally posted by: stepper.sympedia.de
Martin,
I thought about bundling all the sources, too.
But I fear that the potential for multiple versions of the same plugin
forces to have separate source plugins.
This potential might be more important than the minimized effort during
packaging.
Cheers
/Eike
Martin Oberhuber schrieb:
> Hello Eike,
>
> In order to provide sources, even more is needed for each jar:
>
> - One plugin for the binaries
> - One feature for the binary-plugin in update manager
> - Another plugin holding the sources
> - One feature for the sources in update manager
>
> For the source feature I'm not sure, perhaps sources for multiple
> jar's could be packaged into a single source feature? - Perhaps
> that could be another advantage of collecting 3rd party libs in
> the Orbit project, it allows a build process to collect sources
> into a single source feature for update manager.
>
> Cheers,
> Martin
> --
> Martin Oberhuber - WindRiver, Austria
> +43(662)457915-85
>
>
> Eike Stepper wrote:
>> Grahame,
>>
>> I think a plugin per jar is mandatory.
>> To make them available via Update Manager it would be neccessary to
>> provide a feature per plugin.
>> In addition features for larger logical groups of features could be
>> provided.
>>
>> Cheers
>> /Eike
>>
>>
>> Grahame Grieve schrieb:
>>
>>> Martin Oberhuber wrote:
>>>
>>>> Hi,
>>>>
>>>> just FYI, the DSDP Target Management Project is planning to bring
>>>> the Jakarta Commons/Net library to Eclipse. We have already
>>>> initiated the
>>>> EMO review process in May, and since the Apache license is deemed
>>>> compatible, we hope that to complete soon.
>>>
>>>
>>> do we have to go through the legal process for Apache code? I didn't
>>> think that we do?
>>>
>>>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>>> instead of ur own, if others are interested too.
>>>
>>>
>>> Orbit should bring all of Jakarta commons across - different projects
>>> use different parts of it, so I'm not sure what the right packaging
>>> solution is.
>>>
>>> Grahame
|
|
| |
| Re: Jakarta Commons / Net [message #560901 is a reply to message #2953] |
Tue, 11 July 2006 17:29 |
|
Grahame,
I think a plugin per jar is mandatory.
To make them available via Update Manager it would be neccessary to
provide a feature per plugin.
In addition features for larger logical groups of features could be
provided.
Cheers
/Eike
Grahame Grieve schrieb:
> Martin Oberhuber wrote:
>> Hi,
>>
>> just FYI, the DSDP Target Management Project is planning to bring the
>> Jakarta Commons/Net library to Eclipse. We have already initiated the
>> EMO review process in May, and since the Apache license is deemed
>> compatible, we hope that to complete soon.
>
> do we have to go through the legal process for Apache code? I didn't
> think that we do?
>
>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>> instead of ur own, if others are interested too.
>
> Orbit should bring all of Jakarta commons across - different projects
> use different parts of it, so I'm not sure what the right packaging
> solution is.
>
> Grahame
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: Jakarta Commons / Net [message #560914 is a reply to message #3001] |
Tue, 11 July 2006 19:17 |
Sri Doddapaneni
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
In response to Grahame Grieve's comment:
>> do we have to go through the legal process for Apache code? I didn't
>> think that we do?
You have to go thorugh EMO legal review and approval for all thrid-party
code which includes Apache code. You may take comfort in the fact that many
of the Apache components listed are already for use in the context of TPTP
project, possibly by other projects as well. In TPTP, we have been bundling
Apache Commons Logging, Log4J and some others. For these packages, the
overhead of extending use of other Eclipse project should low on the EMO
Legal and hence possiblity of quicker turnaround.
-Sri Doddapaneni
TPTP Project
"Eike Stepper" <stepper@sympedia.de> wrote in message
news:e90n5o$gfn$1@utils.eclipse.org...
> Grahame,
>
> I think a plugin per jar is mandatory.
> To make them available via Update Manager it would be neccessary to
> provide a feature per plugin.
> In addition features for larger logical groups of features could be
> provided.
>
> Cheers
> /Eike
>
>
> Grahame Grieve schrieb:
>> Martin Oberhuber wrote:
>>> Hi,
>>>
>>> just FYI, the DSDP Target Management Project is planning to bring the
>>> Jakarta Commons/Net library to Eclipse. We have already initiated the
>>> EMO review process in May, and since the Apache license is deemed
>>> compatible, we hope that to complete soon.
>>
>> do we have to go through the legal process for Apache code? I didn't
>> think that we do?
>>
>>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>> instead of ur own, if others are interested too.
>>
>> Orbit should bring all of Jakarta commons across - different projects
>> use different parts of it, so I'm not sure what the right packaging
>> solution is.
>>
>> Grahame
|
|
|
| Re: Jakarta Commons / Net [message #560927 is a reply to message #3018] |
Tue, 11 July 2006 20:41 |
Grahame Grieve
Messages: 76
Registered: July 2009 |
Member |
|
|
So, if orbit includes a package, then we wouldn't have to go through
the EMO legal review process to use it, on the basis that it's already
done?
Grahame
Sri Doddapaneni wrote:
> In response to Grahame Grieve's comment:
>>> do we have to go through the legal process for Apache code? I didn't
>>> think that we do?
>
> You have to go thorugh EMO legal review and approval for all thrid-party
> code which includes Apache code. You may take comfort in the fact that many
> of the Apache components listed are already for use in the context of TPTP
> project, possibly by other projects as well. In TPTP, we have been bundling
> Apache Commons Logging, Log4J and some others. For these packages, the
> overhead of extending use of other Eclipse project should low on the EMO
> Legal and hence possiblity of quicker turnaround.
> -Sri Doddapaneni
> TPTP Project
>
>
> "Eike Stepper" <stepper@sympedia.de> wrote in message
> news:e90n5o$gfn$1@utils.eclipse.org...
>> Grahame,
>>
>> I think a plugin per jar is mandatory.
>> To make them available via Update Manager it would be neccessary to
>> provide a feature per plugin.
>> In addition features for larger logical groups of features could be
>> provided.
>>
>> Cheers
>> /Eike
>>
>>
>> Grahame Grieve schrieb:
>>> Martin Oberhuber wrote:
>>>> Hi,
>>>>
>>>> just FYI, the DSDP Target Management Project is planning to bring the
>>>> Jakarta Commons/Net library to Eclipse. We have already initiated the
>>>> EMO review process in May, and since the Apache license is deemed
>>>> compatible, we hope that to complete soon.
>>> do we have to go through the legal process for Apache code? I didn't
>>> think that we do?
>>>
>>>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>>> instead of ur own, if others are interested too.
>>> Orbit should bring all of Jakarta commons across - different projects
>>> use different parts of it, so I'm not sure what the right packaging
>>> solution is.
>>>
>>> Grahame
>
>
|
|
| |
| 3rd party redistribution process (was: Jakarta Commons / Net) [message #561103 is a reply to message #3018] |
Thu, 13 July 2006 07:50 |
Martin Oberhuber
Messages: 1007
Registered: July 2009 |
Senior Member |
|
|
Hello Sri,
As we are going to set up Eclipse projects as containers for
Jakarta Commons Net and ORO, I'm looking for "templates" or
other pointers that help me doing so.
I'm currently looking at the org.apache.ant project, so what
I'm planning to do is
- check in the original *.jar files,
- create and checkin *.zip files to hold the sources
(need to create new ones to factor out examples we don't
want to redistribute)
- create new wrapper .classpath and Manifest.mf files
From your experience, does this approach make sense? IMHO, one
disadvantage of this seems to be that we cannot create JAR'ed
plugins, so Webstart won't be possible. For JAR'ed plugins we'd
have to replace the Manifest.MF and add about.html to the
original *.jar, but I'd rather not touch the original binary...
Does anybody have comments on the process?
Could you point me to the places where Log4J and others are hosted
in the TPTP CVS Repository, such that I can also look at these as
a template? I'm wondering how to do the Features for the Update
Manager for instance.
Do you have any other supporting information that might help me?
Thanks,
Martin
--
Martin Oberhuber - WindRiver, Austria
+43(662)457915-85
Sri Doddapaneni wrote:
> In response to Grahame Grieve's comment:
>
>>>do we have to go through the legal process for Apache code? I didn't
>>>think that we do?
>
>
> You have to go thorugh EMO legal review and approval for all thrid-party
> code which includes Apache code. You may take comfort in the fact that many
> of the Apache components listed are already for use in the context of TPTP
> project, possibly by other projects as well. In TPTP, we have been bundling
> Apache Commons Logging, Log4J and some others. For these packages, the
> overhead of extending use of other Eclipse project should low on the EMO
> Legal and hence possiblity of quicker turnaround.
> -Sri Doddapaneni
> TPTP Project
>
>
> "Eike Stepper" <stepper@sympedia.de> wrote in message
> news:e90n5o$gfn$1@utils.eclipse.org...
>
>>Grahame,
>>
>>I think a plugin per jar is mandatory.
>>To make them available via Update Manager it would be neccessary to
>>provide a feature per plugin.
>>In addition features for larger logical groups of features could be
>>provided.
>>
>>Cheers
>>/Eike
>>
>>
>>Grahame Grieve schrieb:
>>
>>>Martin Oberhuber wrote:
>>>
>>>>Hi,
>>>>
>>>>just FYI, the DSDP Target Management Project is planning to bring the
>>>>Jakarta Commons/Net library to Eclipse. We have already initiated the
>>>>EMO review process in May, and since the Apache license is deemed
>>>>compatible, we hope that to complete soon.
>>>
>>>do we have to go through the legal process for Apache code? I didn't
>>>think that we do?
>>>
>>>
>>>>We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>>>instead of ur own, if others are interested too.
>>>
>>>Orbit should bring all of Jakarta commons across - different projects
>>>use different parts of it, so I'm not sure what the right packaging
>>>solution is.
>>>
>>>Grahame
>
>
>
|
|
|
| Re: Jakarta Commons / Net [message #561120 is a reply to message #3001] |
Thu, 13 July 2006 07:54 |
Martin Oberhuber
Messages: 1007
Registered: July 2009 |
Senior Member |
|
|
Hello Eike,
In order to provide sources, even more is needed for each jar:
- One plugin for the binaries
- One feature for the binary-plugin in update manager
- Another plugin holding the sources
- One feature for the sources in update manager
For the source feature I'm not sure, perhaps sources for multiple
jar's could be packaged into a single source feature? - Perhaps
that could be another advantage of collecting 3rd party libs in
the Orbit project, it allows a build process to collect sources
into a single source feature for update manager.
Cheers,
Martin
--
Martin Oberhuber - WindRiver, Austria
+43(662)457915-85
Eike Stepper wrote:
> Grahame,
>
> I think a plugin per jar is mandatory.
> To make them available via Update Manager it would be neccessary to
> provide a feature per plugin.
> In addition features for larger logical groups of features could be
> provided.
>
> Cheers
> /Eike
>
>
> Grahame Grieve schrieb:
>
>> Martin Oberhuber wrote:
>>
>>> Hi,
>>>
>>> just FYI, the DSDP Target Management Project is planning to bring the
>>> Jakarta Commons/Net library to Eclipse. We have already initiated the
>>> EMO review process in May, and since the Apache license is deemed
>>> compatible, we hope that to complete soon.
>>
>>
>> do we have to go through the legal process for Apache code? I didn't
>> think that we do?
>>
>>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>> instead of ur own, if others are interested too.
>>
>>
>> Orbit should bring all of Jakarta commons across - different projects
>> use different parts of it, so I'm not sure what the right packaging
>> solution is.
>>
>> Grahame
|
|
|
| Re: Jakarta Commons / Net [message #561137 is a reply to message #4670] |
Thu, 13 July 2006 08:53 |
|
Martin,
I thought about bundling all the sources, too.
But I fear that the potential for multiple versions of the same plugin
forces to have separate source plugins.
This potential might be more important than the minimized effort during
packaging.
Cheers
/Eike
Martin Oberhuber schrieb:
> Hello Eike,
>
> In order to provide sources, even more is needed for each jar:
>
> - One plugin for the binaries
> - One feature for the binary-plugin in update manager
> - Another plugin holding the sources
> - One feature for the sources in update manager
>
> For the source feature I'm not sure, perhaps sources for multiple
> jar's could be packaged into a single source feature? - Perhaps
> that could be another advantage of collecting 3rd party libs in
> the Orbit project, it allows a build process to collect sources
> into a single source feature for update manager.
>
> Cheers,
> Martin
> --
> Martin Oberhuber - WindRiver, Austria
> +43(662)457915-85
>
>
> Eike Stepper wrote:
>> Grahame,
>>
>> I think a plugin per jar is mandatory.
>> To make them available via Update Manager it would be neccessary to
>> provide a feature per plugin.
>> In addition features for larger logical groups of features could be
>> provided.
>>
>> Cheers
>> /Eike
>>
>>
>> Grahame Grieve schrieb:
>>
>>> Martin Oberhuber wrote:
>>>
>>>> Hi,
>>>>
>>>> just FYI, the DSDP Target Management Project is planning to bring
>>>> the Jakarta Commons/Net library to Eclipse. We have already
>>>> initiated the
>>>> EMO review process in May, and since the Apache license is deemed
>>>> compatible, we hope that to complete soon.
>>>
>>>
>>> do we have to go through the legal process for Apache code? I didn't
>>> think that we do?
>>>
>>>> We'll be happy to have Jakarta Commons/Net live in the Orbit project
>>>> instead of ur own, if others are interested too.
>>>
>>>
>>> Orbit should bring all of Jakarta commons across - different projects
>>> use different parts of it, so I'm not sure what the right packaging
>>> solution is.
>>>
>>> Grahame
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Goto Forum:
Current Time: Sat Apr 20 02:09:53 GMT 2024
Powered by FUDForum. Page generated in 0.04047 seconds |
] 
Search
Help
Register
Login
Home
