Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] On handling of generated code 
Agreed. Developer-related discussions should happen on m2e-dev list.

As for "cannot complete the install", this is really a p2 user question.
Something in your installation prevents m2e upgrade, so you need to find
what that is and uninstall it. Or start with a fresh eclipse install.

You may also want to wait until m2e 1.1 M3 becomes available as
development/snapshot builds are really targeted at m2e developers and
advanced users interested in helping with m2e development.

--
Regards

On 11-10-22 10:42 AM, Steve Cohen wrote:

It pains me to say this but my thread has been "hijacked". I still don't
have any answers to my questions that I can use.

This list reads more like a developer's list than it does a user's list.
I have great respect for the developers who are building m2e, and the
magnitude of the task that they have undertaken, but I still must say
that some people would rather just be able to use m2e and not worry
about the details. I cannot afford to spend 25% of my development cycles
worrying about m2e. I cannot propogate m2e to OTHER developers on my
team if I don't fully understand it myself. That does not appear to be
possible. There is not enough end-user documentation. I want to have a
comfort zone where things mostly work and the (few) things that don't
work have well-defined workarounds.

Frequently the answers to questions are of the nature "install the
latest beta version". Which if you will look upthread you will see that
I tried to do so, but was met with a

"Cannot complete the install because of a conflicting dependency."

to which no one has responded. Can someone please do so? Must I
uninstall 1.0 to install 1.1?

Advice seems to weave in and out of how to write plugins vs how to use
them with no clear border between them.

Yet and still, I find some useful advice. Such as that I should not be
using the Run As -> Maven this or that as much as I do. Which I had sort
of becoming convinced of myself. Except sometimes it's useful to see the
maven console which I don't see when the system is running maven. Is
there a way to see what Maven is doing when Eclipse is running it?

Years ago the infamous computer "pundit" Jerry Pournelle described dBASE
as an "infuriatingly excellent" product. That's sums up my reaction to m2e.

<end of rant>


On 10/21/2011 01:59 PM, Igor Fedorenko wrote:

In 1.0, You can suppress the error marker by adding <ignore/> mapping in
one of your parent poms.

In 1.1, you can embed <execute/> mapping with runOnIncremental=false and
runOnConfiguration=true in the plugin jar. This is expected to get rid
of the error marker, add java project source folder(s) and run code
generation of full workspace build. You still need to refresh workspace
manually after full workspace build, unless the mojo uses BuildContext.

Alternatively, map the mojo to <ignore/> in the plugin jar, and manage
build classpath and code generation manually. m2e 1.1 preserves custom
classpath entries, so you won't need to manually reconfigure classpath
after each project configuration update.

--
Regards,
Igor

On 11-10-21 1:06 PM, Vegard Havdal wrote:


Den 21. okt. 2011 kl. 17.11 skrev Igor Fedorenko:


Been doing that for years, it works well for the codegen plugins I am
using.



This maybe okay for an internal plugin used by a small closed group of
developers working together, but is bad for opensource maven plugins
with distributed and disconnected user base.


Yes I understand this, but what if you have pretty simple codegen
plugins that have been around a while, and almost always either work
or throw. This is the case for us, pretty big, closed org. Some use
Eclipse, some not. We have been happy to execute generate-sources as
part of project import, via Run As or even outside of Eclipse.

What I am trying to achieve is:

1) Get rid of the red marker in pom.xml (lifecycle config in the
plugin fixes this, so thanks again)
end less important
2) Make Update project configuration add the source folder to the
Eclipse build path

Actually, if there were a way in Eclipse to mute the red marker, that
would be enough for us I think.

Vegard


_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users




_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

Back to the top