You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Nikita Timofeev <nt...@objectstyle.com> on 2022/07/28 11:44:02 UTC
Ant and eclipse related things in the pom.xml
Hi all,
I'm cleaning up project structure a bit. And I have a question about
things that I don't use and don't really know.
1. Ant and vpp dependency. This one is really the last that prevents
us from switching to the Maven Central repo instead of the custom one
we are using, I want to change a bit this feature and use reflection
to get rid of compile-time dependency. Is there anything I need to
worry about?
2. We have some sort of eclipse support in the main pom.xml [1] and I
don't know if it is still useful in any way and is there anybody
willing to support that. I want to just drop it completely, but wanted
to be sure.
[1] https://github.com/apache/cayenne/blob/master/pom.xml#L512
--
Best regards,
Nikita Timofeev
Re: Ant and eclipse related things in the pom.xml
Posted by Mike Kienenberger <mk...@gmail.com>.
> I remember, you mentioned it before. This is sad.
Yes, the last "new" project we used for Cayenne was in 2018, and that
was pretty much copying a small bit of the code base from my 3.1 app
into a small web service.
Actually, that project is using Cayenne 4.1 and maven. I thought
something was, but I had forgotten about this little web service.
On Mon, Aug 1, 2022 at 12:12 PM Andrus Adamchik <aa...@gmail.com> wrote:
>
>
>
> > On Aug 1, 2022, at 5:19 PM, Mike Kienenberger <mk...@gmail.com> wrote:
> >
> > Unfortunately, my most "up-to-date" cayenne project uses 3.x and it is
> > likely being replaced at the end of the year, which is why I haven't
> > commented much on Cayenne 5.0.
>
> I remember, you mentioned it before. This is sad.
>
> FWIW, we have other orgs migrating their whole codebases *to* Cayenne and also looking at Agrest.io on top of it. So maybe the management needs a fresh pitch? :) Anyways, I am kidding. I am sure it was a conscious decision. It is what it is.
>
> Andrus
Re: Ant and eclipse related things in the pom.xml
Posted by Mike Kienenberger <mk...@gmail.com>.
[Offlist]
> So maybe the management needs a fresh pitch? :) Anyways, I am kidding. I am sure it was a conscious decision. It is what it is.
Yeah, the management in this case is the current president of the
utility, and he's decided to do away with custom applications
entirely. Everything is being replaced with an off-the-shelf
product, and, while it's never been admitted out loud, he's probably
doing away with the IT department as well.
4 of the 7 full-time employees have left over the last year, with none
of them being replaced. I tried to get a straight answer from my
manager back in May as to whether my contract would be renewed at the
end of the year, but while he was effusive about how he planned to
renew my contract, when pressed he couldn't give me any examples of
what I might be working on next year.
On Mon, Aug 1, 2022 at 12:12 PM Andrus Adamchik <aa...@gmail.com> wrote:
>
>
>
> > On Aug 1, 2022, at 5:19 PM, Mike Kienenberger <mk...@gmail.com> wrote:
> >
> > Unfortunately, my most "up-to-date" cayenne project uses 3.x and it is
> > likely being replaced at the end of the year, which is why I haven't
> > commented much on Cayenne 5.0.
>
> I remember, you mentioned it before. This is sad.
>
> FWIW, we have other orgs migrating their whole codebases *to* Cayenne and also looking at Agrest.io on top of it. So maybe the management needs a fresh pitch? :) Anyways, I am kidding. I am sure it was a conscious decision. It is what it is.
>
> Andrus
Re: Ant and eclipse related things in the pom.xml
Posted by Andrus Adamchik <aa...@gmail.com>.
> On Aug 1, 2022, at 5:19 PM, Mike Kienenberger <mk...@gmail.com> wrote:
>
> Unfortunately, my most "up-to-date" cayenne project uses 3.x and it is
> likely being replaced at the end of the year, which is why I haven't
> commented much on Cayenne 5.0.
I remember, you mentioned it before. This is sad.
FWIW, we have other orgs migrating their whole codebases *to* Cayenne and also looking at Agrest.io on top of it. So maybe the management needs a fresh pitch? :) Anyways, I am kidding. I am sure it was a conscious decision. It is what it is.
Andrus
Re: Ant and eclipse related things in the pom.xml
Posted by Andrus Adamchik <aa...@gmail.com>.
Thanks, Mike! That makes it easy :)
> If it's important to me or to someone else in the
> future, we can look into adding it back, but there are probably easier
> ways to do these things these days.
I agree.
Andrus
> On Aug 1, 2022, at 5:19 PM, Mike Kienenberger <mk...@gmail.com> wrote:
>
> Was I the culprit? I guess I might have been.
>
> It's only used to provide ant support to injecting dependencies into
> velocity templates, if I recall correctly.
>
> I'd say drop it. If it's important to me or to someone else in the
> future, we can look into adding it back, but there are probably easier
> ways to do these things these days.
>
> Unfortunately, my most "up-to-date" cayenne project uses 3.x and it is
> likely being replaced at the end of the year, which is why I haven't
> commented much on Cayenne 5.0.
>
> On Mon, Aug 1, 2022 at 3:22 AM Andrus Adamchik <aa...@gmail.com> wrote:
>>
>>
>>> On Jul 28, 2022, at 1:44 PM, Nikita Timofeev <nt...@objectstyle.com> wrote:
>>>
>>> 1. Ant and vpp dependency. This one is really the last that prevents
>>> us from switching to the Maven Central repo instead of the custom one
>>> we are using, I want to change a bit this feature and use reflection
>>> to get rid of compile-time dependency. Is there anything I need to
>>> worry about?
>>
>> IIRC, Mike Kienenberger used (and contributed to) VPP integration. Mike, maybe you have any comments? Is this something you'd still use in the future Cayenne 5.0?
>>
>> Andrus
>>
>>
Re: Ant and eclipse related things in the pom.xml
Posted by Mike Kienenberger <mk...@gmail.com>.
Was I the culprit? I guess I might have been.
It's only used to provide ant support to injecting dependencies into
velocity templates, if I recall correctly.
I'd say drop it. If it's important to me or to someone else in the
future, we can look into adding it back, but there are probably easier
ways to do these things these days.
Unfortunately, my most "up-to-date" cayenne project uses 3.x and it is
likely being replaced at the end of the year, which is why I haven't
commented much on Cayenne 5.0.
On Mon, Aug 1, 2022 at 3:22 AM Andrus Adamchik <aa...@gmail.com> wrote:
>
>
> > On Jul 28, 2022, at 1:44 PM, Nikita Timofeev <nt...@objectstyle.com> wrote:
> >
> > 1. Ant and vpp dependency. This one is really the last that prevents
> > us from switching to the Maven Central repo instead of the custom one
> > we are using, I want to change a bit this feature and use reflection
> > to get rid of compile-time dependency. Is there anything I need to
> > worry about?
>
> IIRC, Mike Kienenberger used (and contributed to) VPP integration. Mike, maybe you have any comments? Is this something you'd still use in the future Cayenne 5.0?
>
> Andrus
>
>
Re: Ant and eclipse related things in the pom.xml
Posted by Andrus Adamchik <aa...@gmail.com>.
> On Jul 28, 2022, at 1:44 PM, Nikita Timofeev <nt...@objectstyle.com> wrote:
>
> 1. Ant and vpp dependency. This one is really the last that prevents
> us from switching to the Maven Central repo instead of the custom one
> we are using, I want to change a bit this feature and use reflection
> to get rid of compile-time dependency. Is there anything I need to
> worry about?
IIRC, Mike Kienenberger used (and contributed to) VPP integration. Mike, maybe you have any comments? Is this something you'd still use in the future Cayenne 5.0?
Andrus
Re: Ant and eclipse related things in the pom.xml
Posted by Nikita Timofeev <nt...@objectstyle.com>.
If you are ready to keep it in a somewhat descent shape that would be
wonderful.
On Fri, Jul 29, 2022 at 1:06 AM John Huss <jo...@gmail.com> wrote:
>
> On Thu, Jul 28, 2022 at 6:44 AM Nikita Timofeev <nt...@objectstyle.com>
> wrote:
>
> > Hi all,
> >
> > I'm cleaning up project structure a bit. And I have a question about
> > things that I don't use and don't really know.
> >
> > 1. Ant and vpp dependency. This one is really the last that prevents
> > us from switching to the Maven Central repo instead of the custom one
> > we are using, I want to change a bit this feature and use reflection
> > to get rid of compile-time dependency. Is there anything I need to
> > worry about?
> >
> > 2. We have some sort of eclipse support in the main pom.xml [1] and I
> > don't know if it is still useful in any way and is there anybody
> > willing to support that. I want to just drop it completely, but wanted
> > to be sure.
> >
>
> At the least, this code block prevents eclipse from displaying errors for
> the project saying "Plugin execution not covered by lifecycle
> configuration". I don't believe it does much more than that. I do use
> eclipse, so I find that helpful. But it seems to only be a display issue. I
> don't know much about maven/eclipse integration so I don't know if there is
> another or better way to do this.
>
> If you are going to keep it I can submit a patch to add the 2 phases that
> are currently missing from that block and will try to keep it up to date in
> that way going forward.
>
>
> >
> > [1] https://github.com/apache/cayenne/blob/master/pom.xml#L512
> >
> > --
> > Best regards,
> > Nikita Timofeev
> >
--
Best regards,
Nikita Timofeev
Re: Ant and eclipse related things in the pom.xml
Posted by John Huss <jo...@gmail.com>.
On Thu, Jul 28, 2022 at 6:44 AM Nikita Timofeev <nt...@objectstyle.com>
wrote:
> Hi all,
>
> I'm cleaning up project structure a bit. And I have a question about
> things that I don't use and don't really know.
>
> 1. Ant and vpp dependency. This one is really the last that prevents
> us from switching to the Maven Central repo instead of the custom one
> we are using, I want to change a bit this feature and use reflection
> to get rid of compile-time dependency. Is there anything I need to
> worry about?
>
> 2. We have some sort of eclipse support in the main pom.xml [1] and I
> don't know if it is still useful in any way and is there anybody
> willing to support that. I want to just drop it completely, but wanted
> to be sure.
>
At the least, this code block prevents eclipse from displaying errors for
the project saying "Plugin execution not covered by lifecycle
configuration". I don't believe it does much more than that. I do use
eclipse, so I find that helpful. But it seems to only be a display issue. I
don't know much about maven/eclipse integration so I don't know if there is
another or better way to do this.
If you are going to keep it I can submit a patch to add the 2 phases that
are currently missing from that block and will try to keep it up to date in
that way going forward.
>
> [1] https://github.com/apache/cayenne/blob/master/pom.xml#L512
>
> --
> Best regards,
> Nikita Timofeev
>