You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Jonathan Gallimore <jo...@gmail.com> on 2009/04/30 16:34:44 UTC
Eclipse plugin update
Hi All,
Just wanted to let you know that I've done a couple of enhancements on the
Eclipse plugin (Jiras OEP-28 and OEP-29) - one is to keep the name attribute
from ejb-jar.xml when generating an @EJB annotation, and the other is fixing
an issue when generating @RemoteHome annotations - we were generating both
@Remote and @RemoteHome, and the resulting code wouldn't deploy.
I've committed this and updated the update site, please let me know if you
have any problems.
Cheers
Jon
Re: Eclipse plugin update
Posted by "Daniel S. Haischt" <da...@googlemail.com>.
The so-called update site is either an online or offline repository
containing both the actual binary artifacts of the product and and
accompanying metadata which is needed to install the product into an
existing Eclipse SDK.
If the plug-in is getting distributed online, an HTTP server is
required to server the directory containing the metadata (site.xml
etc.). An alternative would be to distribute the update site as a ZIP
archive and the user would then be able to download it and us it as an
offline update site by pointing the Eclipse update manager to the
archived update site.
On Thu, May 14, 2009 at 4:42 AM, David Blevins <da...@visi.com> wrote:
>
> On May 13, 2009, at 3:52 PM, Jonathan Gallimore wrote:
>
>> I don't know that we need to do anything on the Eclipse side of things
>> other
>> than decide where we want to host the update site from, and advertise the
>> plugin a little.
>
> So is this a special distribution mechanism like with maven? Wondering how
> it works and if there's any possibility to get the mirrors involved.
>
>> I agree on getting an alpha release out totally, I've been meaning to do
>> it
>> for ages. In terms of SVN is there anything that we need to do, do we need
>> to move the code from the sandbox folder - we presumably need to consider
>> how we tag/branch the plugin as well?
>>
>> I'm happy to get this going - is it as simple as just building the
>> binaries
>> and starting a vote, or is there anything else that needs to be done?
>
> SVN-wise the ultimate goal is to have a tag for the release. To get there
> we probably do want to get the stuff moved into trunk from sandbox. There
> is a maven plugin which is helps with finalizing all the version numbers in
> the poms and publishing to the maven repo, but I'm not sure if we need/want
> to put eclipse plugin stuff in the maven repo (will people be writing maven
> modules that use parts of the plugin?).
>
> Doing things by hand is fine otherwise. That's basically a process of
> creating a branch, finalizing the versions, build and sign the binaries,
> push them to a staging place somewhere, start vote, and finally publish or
> start over.
>
> Definitely going to need a PGP key for signing the binaries. (see
> http://www.apache.org/dist/openejb/KEYS)
>
> Might also need to get you a login for repository.apache.org so you can
> publish any jars to the maven repo that may need to be published.
>
> Legal-wise we're going to need a LICENSE.txt and a NOTICE.txt for each
> binary. See the ones in the openejb-3.1.zip for an example. We'll also
> need to make sure we have license headers on any source files that need them
> -- seem to always be a few that slip through the cracks.
>
>
> -David
>
>
>> On Wed, May 13, 2009 at 11:17 AM, Daniel S. Haischt <
>> daniel.haischt@googlemail.com> wrote:
>>
>>> what do you mean by "on the eclipse side of things" ?
>>>
>>> On Wed, May 13, 2009 at 1:12 AM, David Blevins <da...@visi.com>
>>> wrote:
>>>>
>>>> On Apr 30, 2009, at 7:34 AM, Jonathan Gallimore wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> Just wanted to let you know that I've done a couple of enhancements on
>>>
>>> the
>>>>>
>>>>> Eclipse plugin (Jiras OEP-28 and OEP-29) - one is to keep the name
>>>>> attribute
>>>>> from ejb-jar.xml when generating an @EJB annotation, and the other is
>>>>> fixing
>>>>> an issue when generating @RemoteHome annotations - we were generating
>>>
>>> both
>>>>>
>>>>> @Remote and @RemoteHome, and the resulting code wouldn't deploy.
>>>>>
>>>>> I've committed this and updated the update site, please let me know if
>>>
>>> you
>>>>>
>>>>> have any problems.
>>>>
>>>> I think we should get some kind of a release up for this thing. Even an
>>>> alpha or beta is good. Thinking primarily with my legal hat on -- we
>>>
>>> should
>>>>
>>>> get something to distribute that has gone through a vote, etc.
>>>>
>>>> Not sure what we need to do on the eclipse side of things to release
>>>
>>> though.
>>>>
>>>> Thoughts?
>>>>
>>>> -David
>>>>
>>>>
>>>
>
>
Re: Eclipse plugin update
Posted by Jonathan Gallimore <jo...@gmail.com>.
If you're sure, I'm happy to move the directory this afternoon. I'm quite
happy to wait and get a structure we're all happy with though.
Cheers
Jon
On Mon, May 25, 2009 at 12:07 PM, Jacek Laskowski <ja...@laskowski.net.pl>wrote:
> On Mon, May 25, 2009 at 12:57 PM, Jonathan Gallimore
> <jo...@gmail.com> wrote:
> > Just to clarify, what you'd like to see is a structure like this:
> >
> > https://svn.apache.org/repos/asf/openejb
> > -- openejb3
> > -- trunk
> > -- branches
> > -- tags
> > -- openejb-eclipse-plugin
> > -- trunk
> > -- branches
> > -- tags
>
> Yes.
>
> > You mention that it could be moved when the main parts of OpenEJB are
> moved
> > to a subdirectory - are there plans to do this?
>
> Not that I'm aware of. It's not gonna happen by 3.1.1, so I can
> withdraw my proposal and let the things move on (and fix them
> afterwards).
>
> Jacek
>
> --
> Jacek Laskowski
> Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
>
Re: Eclipse plugin update
Posted by Jonathan Gallimore <jo...@gmail.com>.
I've moved the openejb-eclipse-plugin directory up one level. I've also
committed the work for the Invalid Runtime issue, and got the plugin working
on both 32 and 64 bit linux.
I'm going to run some tests, and try and get some binaries up for review :)
Jon
On Mon, May 25, 2009 at 7:19 PM, David Blevins <da...@visi.com>wrote:
>
> On May 25, 2009, at 4:07 AM, Jacek Laskowski wrote:
>
> You mention that it could be moved when the main parts of OpenEJB are
>>> moved
>>> to a subdirectory - are there plans to do this?
>>>
>>
>> Not that I'm aware of. It's not gonna happen by 3.1.1, so I can
>> withdraw my proposal and let the things move on (and fix them
>> afterwards).
>>
>
> I'm not sure it's really worth it. All the email archive history where svn
> paths are used will now all be wrong. Vote threads, tech discussion
> threads, and user threads where we say "check out this example" all will
> point to invalid paths. And sites like ohloh.net still can't handle when
> things get moved at the root (that's why we don't have any history before
> 2006 on that site).
>
> -David
>
>
Re: Eclipse plugin update
Posted by David Blevins <da...@visi.com>.
On May 25, 2009, at 4:07 AM, Jacek Laskowski wrote:
>> You mention that it could be moved when the main parts of OpenEJB
>> are moved
>> to a subdirectory - are there plans to do this?
>
> Not that I'm aware of. It's not gonna happen by 3.1.1, so I can
> withdraw my proposal and let the things move on (and fix them
> afterwards).
I'm not sure it's really worth it. All the email archive history
where svn paths are used will now all be wrong. Vote threads, tech
discussion threads, and user threads where we say "check out this
example" all will point to invalid paths. And sites like ohloh.net
still can't handle when things get moved at the root (that's why we
don't have any history before 2006 on that site).
-David
Re: Eclipse plugin update
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On Mon, May 25, 2009 at 12:57 PM, Jonathan Gallimore
<jo...@gmail.com> wrote:
> Just to clarify, what you'd like to see is a structure like this:
>
> https://svn.apache.org/repos/asf/openejb
> -- openejb3
> -- trunk
> -- branches
> -- tags
> -- openejb-eclipse-plugin
> -- trunk
> -- branches
> -- tags
Yes.
> You mention that it could be moved when the main parts of OpenEJB are moved
> to a subdirectory - are there plans to do this?
Not that I'm aware of. It's not gonna happen by 3.1.1, so I can
withdraw my proposal and let the things move on (and fix them
afterwards).
Jacek
--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
Re: Eclipse plugin update
Posted by Jonathan Gallimore <jo...@gmail.com>.
Just to clarify, what you'd like to see is a structure like this:
https://svn.apache.org/repos/asf/openejb
-- openejb3
-- trunk
-- branches
-- tags
-- openejb-eclipse-plugin
-- trunk
-- branches
-- tags
rather than
https://svn.apache.org/repos/asf/openejb
-- trunk
-- openejb3
-- openejb-eclipse-plugin
-- branches
-- openejb3
-- openejb-eclipse-plugin
-- tags
-- openejb3
-- openejb-eclipse-plugin
In an ideal world, I prefer the first of the two, but obviously this will be
a bigger change, and will affect a lot more people.
You mention that it could be moved when the main parts of OpenEJB are moved
to a subdirectory - are there plans to do this?
Cheers
Jon
On Mon, May 25, 2009 at 7:20 AM, Jacek Laskowski <ja...@laskowski.net.pl>wrote:
> On Sun, May 24, 2009 at 8:15 PM, Jonathan Gallimore
> <jo...@gmail.com> wrote:
>
> > Are there any objections to me copying
> >
> https://svn.apache.org/repos/asf/openejb/trunk/sandbox/openejb-eclipse-plugin/up
> > to
> > https://svn.apache.org/repos/asf/openejb/trunk/openejb-eclipse-plugin/ -
> if
> > not I can get it done tomorrow (public holiday here in the UK :)).
>
> I think it could go to the proposed svn directory structure *when* the
> other parts of openejb moved to a subdirectory so the eclipse plugin
> were not part of the main trunk.
>
> Jacek
>
> --
> Jacek Laskowski
> Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
>
Re: Eclipse plugin update
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On Sun, May 24, 2009 at 8:15 PM, Jonathan Gallimore
<jo...@gmail.com> wrote:
> Are there any objections to me copying
> https://svn.apache.org/repos/asf/openejb/trunk/sandbox/openejb-eclipse-plugin/up
> to
> https://svn.apache.org/repos/asf/openejb/trunk/openejb-eclipse-plugin/ - if
> not I can get it done tomorrow (public holiday here in the UK :)).
I think it could go to the proposed svn directory structure *when* the
other parts of openejb moved to a subdirectory so the eclipse plugin
were not part of the main trunk.
Jacek
--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
Re: Eclipse plugin update
Posted by Jonathan Gallimore <jo...@gmail.com>.
I just replied to Jacek's mail, so I won't do it just yet, so we can discuss
it a little more.
Cheers
Jon
On Mon, May 25, 2009 at 10:08 AM, David Blevins <da...@visi.com>wrote:
>
> On May 24, 2009, at 11:15 AM, Jonathan Gallimore wrote:
>
> Are there any objections to me copying
>>
>> https://svn.apache.org/repos/asf/openejb/trunk/sandbox/openejb-eclipse-plugin/up
>> to
>> https://svn.apache.org/repos/asf/openejb/trunk/openejb-eclipse-plugin/ -
>> if
>> not I can get it done tomorrow (public holiday here in the UK :)).
>>
>
> Seems fine to me.
>
> -David
>
>
>
Re: Eclipse plugin update
Posted by David Blevins <da...@visi.com>.
On May 24, 2009, at 11:15 AM, Jonathan Gallimore wrote:
> Are there any objections to me copying
> https://svn.apache.org/repos/asf/openejb/trunk/sandbox/openejb-eclipse-plugin/up
> to
> https://svn.apache.org/repos/asf/openejb/trunk/openejb-eclipse-
> plugin/ - if
> not I can get it done tomorrow (public holiday here in the UK :)).
Seems fine to me.
-David
Re: Eclipse plugin update
Posted by Jonathan Gallimore <jo...@gmail.com>.
I've set up a PGP key, and read up a bit on deploying releases. I'm not sure
about how to get setup to publish to Nexus at the moment, some pointers
would be great if anyone knows.
There's a couple of issues I'd like to resolve before calling a vote for an
alpha release specifically:
- Fix "invalid runtime" error - https://issues.apache.org/jira/browse/OEP-30
- Fix build so it works for both 32 and 64 bit Linux -
https://issues.apache.org/jira/browse/OEP-31
Are there any objections to me copying
https://svn.apache.org/repos/asf/openejb/trunk/sandbox/openejb-eclipse-plugin/up
to
https://svn.apache.org/repos/asf/openejb/trunk/openejb-eclipse-plugin/ - if
not I can get it done tomorrow (public holiday here in the UK :)). Would
this interfere with the 3.1 branch at all?
Cheers
Jon
On Thu, May 14, 2009 at 11:37 PM, Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:
> On Thu, May 14, 2009 at 3:42 AM, David Blevins <da...@visi.com>wrote:
>
>>
>> On May 13, 2009, at 3:52 PM, Jonathan Gallimore wrote:
>>
>> I don't know that we need to do anything on the Eclipse side of things
>>> other
>>> than decide where we want to host the update site from, and advertise the
>>> plugin a little.
>>>
>>
>> So is this a special distribution mechanism like with maven? Wondering
>> how it works and if there's any possibility to get the mirrors involved.
>>
>
> Really its a set of jars, and descriptor (site.xml). From the assembly part
> of the project we generate two artifacts, one is a zip that can just be
> unzipped and dropped in an Eclipse dropins folder, the other is a zipped
> copy of the update site - see
> http://people.apache.org/~jgallimore/openejb-eclipse-plugin-1.0.2-SNAPSHOT-updatesite.zip<http://people.apache.org/%7Ejgallimore/openejb-eclipse-plugin-1.0.2-SNAPSHOT-updatesite.zip>for an example.
>
> To create the update site that's currently available from my ASF people
> site, I just SCP this zip file up, and unzip it to
> ~/public_html/update-site.
>
> I would imagine we could provide the dropin zip as a download just like the
> openejb.zip, which I guess would be available through the mirrors. I'm not
> sure about how the update site would work with the mirrors, in theory its
> just a directory - would we be able to publish / mirror that? I guess it
> might be worth finding out what the Geronimo Eclipse Plugin guys do.
>
>
>>
>> I agree on getting an alpha release out totally, I've been meaning to do
>>> it
>>> for ages. In terms of SVN is there anything that we need to do, do we
>>> need
>>> to move the code from the sandbox folder - we presumably need to consider
>>> how we tag/branch the plugin as well?
>>>
>>> I'm happy to get this going - is it as simple as just building the
>>> binaries
>>> and starting a vote, or is there anything else that needs to be done?
>>>
>>
>> SVN-wise the ultimate goal is to have a tag for the release. To get there
>> we probably do want to get the stuff moved into trunk from sandbox. There
>> is a maven plugin which is helps with finalizing all the version numbers in
>> the poms and publishing to the maven repo, but I'm not sure if we need/want
>> to put eclipse plugin stuff in the maven repo (will people be writing maven
>> modules that use parts of the plugin?).
>>
>> Doing things by hand is fine otherwise. That's basically a process of
>> creating a branch, finalizing the versions, build and sign the binaries,
>> push them to a staging place somewhere, start vote, and finally publish or
>> start over.
>>
>
> Sounds like we need to move
> https://svn.apache.org/repos/asf/openejb/trunk/sandbox/openejb-eclipse-pluginup one level. Would that work? Presumably branching and tagging would
> branch/tag the whole of the OpenEJB code as well - would that cause any
> problems?
>
> Overall there are now about 14 plugins which actually make up our Eclipse
> tooling, I think the vast majority are only really useful as part of the
> overall feature set, and won't need to be published to the maven repo.
>
> However, the plugin Deryck Brown put together for us I think is the
> exception. This can be deployed in Equinox on its own as part of an OSGi
> solution. I think it would be useful for people to bring this into their
> projects, so if we could offer that via Maven I think that would be useful.
>
>
>
>>
>> Definitely going to need a PGP key for signing the binaries. (see
>> http://www.apache.org/dist/openejb/KEYS)
>>
>> Might also need to get you a login for repository.apache.org so you can
>> publish any jars to the maven repo that may need to be published.
>
>
> I'll have a look at that and see if I can sort myself out with the
> necessary stuff over the weekend.
>
>
>>
>>
>> Legal-wise we're going to need a LICENSE.txt and a NOTICE.txt for each
>> binary. See the ones in the openejb-3.1.zip for an example. We'll also
>> need to make sure we have license headers on any source files that need them
>> -- seem to always be a few that slip through the cracks.
>
>
> I ran the maven rat plugin a while ago, so I think most of the files have
> the correct headers, I'll run it again before rolling some binaries just to
> be sure. I'll also check that we have the necessary LICENSE.txt and
> NOTICE.txt files.
>
> Jon
>
>
>>
>>
>>
>> -David
>>
>>
>>
>> On Wed, May 13, 2009 at 11:17 AM, Daniel S. Haischt <
>>> daniel.haischt@googlemail.com> wrote:
>>>
>>> what do you mean by "on the eclipse side of things" ?
>>>>
>>>> On Wed, May 13, 2009 at 1:12 AM, David Blevins <da...@visi.com>
>>>> wrote:
>>>>
>>>>>
>>>>> On Apr 30, 2009, at 7:34 AM, Jonathan Gallimore wrote:
>>>>>
>>>>> Hi All,
>>>>>>
>>>>>> Just wanted to let you know that I've done a couple of enhancements on
>>>>>>
>>>>> the
>>>>
>>>>> Eclipse plugin (Jiras OEP-28 and OEP-29) - one is to keep the name
>>>>>> attribute
>>>>>> from ejb-jar.xml when generating an @EJB annotation, and the other is
>>>>>> fixing
>>>>>> an issue when generating @RemoteHome annotations - we were generating
>>>>>>
>>>>> both
>>>>
>>>>> @Remote and @RemoteHome, and the resulting code wouldn't deploy.
>>>>>>
>>>>>> I've committed this and updated the update site, please let me know if
>>>>>>
>>>>> you
>>>>
>>>>> have any problems.
>>>>>>
>>>>>
>>>>> I think we should get some kind of a release up for this thing. Even
>>>>> an
>>>>> alpha or beta is good. Thinking primarily with my legal hat on -- we
>>>>>
>>>> should
>>>>
>>>>> get something to distribute that has gone through a vote, etc.
>>>>>
>>>>> Not sure what we need to do on the eclipse side of things to release
>>>>>
>>>> though.
>>>>
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> -David
>>>>>
>>>>>
>>>>>
>>>>
>>
>
Re: Eclipse plugin update
Posted by Jonathan Gallimore <jo...@gmail.com>.
On Thu, May 14, 2009 at 3:42 AM, David Blevins <da...@visi.com>wrote:
>
> On May 13, 2009, at 3:52 PM, Jonathan Gallimore wrote:
>
> I don't know that we need to do anything on the Eclipse side of things
>> other
>> than decide where we want to host the update site from, and advertise the
>> plugin a little.
>>
>
> So is this a special distribution mechanism like with maven? Wondering how
> it works and if there's any possibility to get the mirrors involved.
>
Really its a set of jars, and descriptor (site.xml). From the assembly part
of the project we generate two artifacts, one is a zip that can just be
unzipped and dropped in an Eclipse dropins folder, the other is a zipped
copy of the update site - see
http://people.apache.org/~jgallimore/openejb-eclipse-plugin-1.0.2-SNAPSHOT-updatesite.zipfor
an example.
To create the update site that's currently available from my ASF people
site, I just SCP this zip file up, and unzip it to
~/public_html/update-site.
I would imagine we could provide the dropin zip as a download just like the
openejb.zip, which I guess would be available through the mirrors. I'm not
sure about how the update site would work with the mirrors, in theory its
just a directory - would we be able to publish / mirror that? I guess it
might be worth finding out what the Geronimo Eclipse Plugin guys do.
>
> I agree on getting an alpha release out totally, I've been meaning to do
>> it
>> for ages. In terms of SVN is there anything that we need to do, do we need
>> to move the code from the sandbox folder - we presumably need to consider
>> how we tag/branch the plugin as well?
>>
>> I'm happy to get this going - is it as simple as just building the
>> binaries
>> and starting a vote, or is there anything else that needs to be done?
>>
>
> SVN-wise the ultimate goal is to have a tag for the release. To get there
> we probably do want to get the stuff moved into trunk from sandbox. There
> is a maven plugin which is helps with finalizing all the version numbers in
> the poms and publishing to the maven repo, but I'm not sure if we need/want
> to put eclipse plugin stuff in the maven repo (will people be writing maven
> modules that use parts of the plugin?).
>
> Doing things by hand is fine otherwise. That's basically a process of
> creating a branch, finalizing the versions, build and sign the binaries,
> push them to a staging place somewhere, start vote, and finally publish or
> start over.
>
Sounds like we need to move
https://svn.apache.org/repos/asf/openejb/trunk/sandbox/openejb-eclipse-pluginup
one level. Would that work? Presumably branching and tagging would
branch/tag the whole of the OpenEJB code as well - would that cause any
problems?
Overall there are now about 14 plugins which actually make up our Eclipse
tooling, I think the vast majority are only really useful as part of the
overall feature set, and won't need to be published to the maven repo.
However, the plugin Deryck Brown put together for us I think is the
exception. This can be deployed in Equinox on its own as part of an OSGi
solution. I think it would be useful for people to bring this into their
projects, so if we could offer that via Maven I think that would be useful.
>
> Definitely going to need a PGP key for signing the binaries. (see
> http://www.apache.org/dist/openejb/KEYS)
>
> Might also need to get you a login for repository.apache.org so you can
> publish any jars to the maven repo that may need to be published.
I'll have a look at that and see if I can sort myself out with the necessary
stuff over the weekend.
>
>
> Legal-wise we're going to need a LICENSE.txt and a NOTICE.txt for each
> binary. See the ones in the openejb-3.1.zip for an example. We'll also
> need to make sure we have license headers on any source files that need them
> -- seem to always be a few that slip through the cracks.
I ran the maven rat plugin a while ago, so I think most of the files have
the correct headers, I'll run it again before rolling some binaries just to
be sure. I'll also check that we have the necessary LICENSE.txt and
NOTICE.txt files.
Jon
>
>
>
> -David
>
>
>
> On Wed, May 13, 2009 at 11:17 AM, Daniel S. Haischt <
>> daniel.haischt@googlemail.com> wrote:
>>
>> what do you mean by "on the eclipse side of things" ?
>>>
>>> On Wed, May 13, 2009 at 1:12 AM, David Blevins <da...@visi.com>
>>> wrote:
>>>
>>>>
>>>> On Apr 30, 2009, at 7:34 AM, Jonathan Gallimore wrote:
>>>>
>>>> Hi All,
>>>>>
>>>>> Just wanted to let you know that I've done a couple of enhancements on
>>>>>
>>>> the
>>>
>>>> Eclipse plugin (Jiras OEP-28 and OEP-29) - one is to keep the name
>>>>> attribute
>>>>> from ejb-jar.xml when generating an @EJB annotation, and the other is
>>>>> fixing
>>>>> an issue when generating @RemoteHome annotations - we were generating
>>>>>
>>>> both
>>>
>>>> @Remote and @RemoteHome, and the resulting code wouldn't deploy.
>>>>>
>>>>> I've committed this and updated the update site, please let me know if
>>>>>
>>>> you
>>>
>>>> have any problems.
>>>>>
>>>>
>>>> I think we should get some kind of a release up for this thing. Even an
>>>> alpha or beta is good. Thinking primarily with my legal hat on -- we
>>>>
>>> should
>>>
>>>> get something to distribute that has gone through a vote, etc.
>>>>
>>>> Not sure what we need to do on the eclipse side of things to release
>>>>
>>> though.
>>>
>>>>
>>>> Thoughts?
>>>>
>>>> -David
>>>>
>>>>
>>>>
>>>
>
Re: Eclipse plugin update
Posted by David Blevins <da...@visi.com>.
On May 13, 2009, at 3:52 PM, Jonathan Gallimore wrote:
> I don't know that we need to do anything on the Eclipse side of
> things other
> than decide where we want to host the update site from, and
> advertise the
> plugin a little.
So is this a special distribution mechanism like with maven?
Wondering how it works and if there's any possibility to get the
mirrors involved.
> I agree on getting an alpha release out totally, I've been meaning
> to do it
> for ages. In terms of SVN is there anything that we need to do, do
> we need
> to move the code from the sandbox folder - we presumably need to
> consider
> how we tag/branch the plugin as well?
>
> I'm happy to get this going - is it as simple as just building the
> binaries
> and starting a vote, or is there anything else that needs to be done?
SVN-wise the ultimate goal is to have a tag for the release. To get
there we probably do want to get the stuff moved into trunk from
sandbox. There is a maven plugin which is helps with finalizing all
the version numbers in the poms and publishing to the maven repo, but
I'm not sure if we need/want to put eclipse plugin stuff in the maven
repo (will people be writing maven modules that use parts of the
plugin?).
Doing things by hand is fine otherwise. That's basically a process of
creating a branch, finalizing the versions, build and sign the
binaries, push them to a staging place somewhere, start vote, and
finally publish or start over.
Definitely going to need a PGP key for signing the binaries. (see http://www.apache.org/dist/openejb/KEYS)
Might also need to get you a login for repository.apache.org so you
can publish any jars to the maven repo that may need to be published.
Legal-wise we're going to need a LICENSE.txt and a NOTICE.txt for each
binary. See the ones in the openejb-3.1.zip for an example. We'll
also need to make sure we have license headers on any source files
that need them -- seem to always be a few that slip through the cracks.
-David
> On Wed, May 13, 2009 at 11:17 AM, Daniel S. Haischt <
> daniel.haischt@googlemail.com> wrote:
>
>> what do you mean by "on the eclipse side of things" ?
>>
>> On Wed, May 13, 2009 at 1:12 AM, David Blevins <david.blevins@visi.com
>> >
>> wrote:
>>>
>>> On Apr 30, 2009, at 7:34 AM, Jonathan Gallimore wrote:
>>>
>>>> Hi All,
>>>>
>>>> Just wanted to let you know that I've done a couple of
>>>> enhancements on
>> the
>>>> Eclipse plugin (Jiras OEP-28 and OEP-29) - one is to keep the name
>>>> attribute
>>>> from ejb-jar.xml when generating an @EJB annotation, and the
>>>> other is
>>>> fixing
>>>> an issue when generating @RemoteHome annotations - we were
>>>> generating
>> both
>>>> @Remote and @RemoteHome, and the resulting code wouldn't deploy.
>>>>
>>>> I've committed this and updated the update site, please let me
>>>> know if
>> you
>>>> have any problems.
>>>
>>> I think we should get some kind of a release up for this thing.
>>> Even an
>>> alpha or beta is good. Thinking primarily with my legal hat on --
>>> we
>> should
>>> get something to distribute that has gone through a vote, etc.
>>>
>>> Not sure what we need to do on the eclipse side of things to release
>> though.
>>>
>>> Thoughts?
>>>
>>> -David
>>>
>>>
>>
Re: Eclipse plugin update
Posted by Jonathan Gallimore <jo...@gmail.com>.
I don't know that we need to do anything on the Eclipse side of things other
than decide where we want to host the update site from, and advertise the
plugin a little.
I agree on getting an alpha release out totally, I've been meaning to do it
for ages. In terms of SVN is there anything that we need to do, do we need
to move the code from the sandbox folder - we presumably need to consider
how we tag/branch the plugin as well?
I'm happy to get this going - is it as simple as just building the binaries
and starting a vote, or is there anything else that needs to be done?
Cheers
Jon
On Wed, May 13, 2009 at 11:17 AM, Daniel S. Haischt <
daniel.haischt@googlemail.com> wrote:
> what do you mean by "on the eclipse side of things" ?
>
> On Wed, May 13, 2009 at 1:12 AM, David Blevins <da...@visi.com>
> wrote:
> >
> > On Apr 30, 2009, at 7:34 AM, Jonathan Gallimore wrote:
> >
> >> Hi All,
> >>
> >> Just wanted to let you know that I've done a couple of enhancements on
> the
> >> Eclipse plugin (Jiras OEP-28 and OEP-29) - one is to keep the name
> >> attribute
> >> from ejb-jar.xml when generating an @EJB annotation, and the other is
> >> fixing
> >> an issue when generating @RemoteHome annotations - we were generating
> both
> >> @Remote and @RemoteHome, and the resulting code wouldn't deploy.
> >>
> >> I've committed this and updated the update site, please let me know if
> you
> >> have any problems.
> >
> > I think we should get some kind of a release up for this thing. Even an
> > alpha or beta is good. Thinking primarily with my legal hat on -- we
> should
> > get something to distribute that has gone through a vote, etc.
> >
> > Not sure what we need to do on the eclipse side of things to release
> though.
> >
> > Thoughts?
> >
> > -David
> >
> >
>
Re: Eclipse plugin update
Posted by "Daniel S. Haischt" <da...@googlemail.com>.
what do you mean by "on the eclipse side of things" ?
On Wed, May 13, 2009 at 1:12 AM, David Blevins <da...@visi.com> wrote:
>
> On Apr 30, 2009, at 7:34 AM, Jonathan Gallimore wrote:
>
>> Hi All,
>>
>> Just wanted to let you know that I've done a couple of enhancements on the
>> Eclipse plugin (Jiras OEP-28 and OEP-29) - one is to keep the name
>> attribute
>> from ejb-jar.xml when generating an @EJB annotation, and the other is
>> fixing
>> an issue when generating @RemoteHome annotations - we were generating both
>> @Remote and @RemoteHome, and the resulting code wouldn't deploy.
>>
>> I've committed this and updated the update site, please let me know if you
>> have any problems.
>
> I think we should get some kind of a release up for this thing. Even an
> alpha or beta is good. Thinking primarily with my legal hat on -- we should
> get something to distribute that has gone through a vote, etc.
>
> Not sure what we need to do on the eclipse side of things to release though.
>
> Thoughts?
>
> -David
>
>
Re: Eclipse plugin update
Posted by David Blevins <da...@visi.com>.
On Apr 30, 2009, at 7:34 AM, Jonathan Gallimore wrote:
> Hi All,
>
> Just wanted to let you know that I've done a couple of enhancements
> on the
> Eclipse plugin (Jiras OEP-28 and OEP-29) - one is to keep the name
> attribute
> from ejb-jar.xml when generating an @EJB annotation, and the other
> is fixing
> an issue when generating @RemoteHome annotations - we were
> generating both
> @Remote and @RemoteHome, and the resulting code wouldn't deploy.
>
> I've committed this and updated the update site, please let me know
> if you
> have any problems.
I think we should get some kind of a release up for this thing. Even
an alpha or beta is good. Thinking primarily with my legal hat on --
we should get something to distribute that has gone through a vote, etc.
Not sure what we need to do on the eclipse side of things to release
though.
Thoughts?
-David