Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-dev] compiling for first time

I often find this a painful part of contributing to a project, i.e., getting the launch configurations configured correctly.  Should it be a Junit or a JUnit Plugin test.  Should it be headless in the latter case?  Maintaining the launch configurations in the project seems a good idea.  But then one often doesn't notice that the launch configurations are in fact there, just not in the favorites list.  I see a "JDT Debug Test Suite" is maintained in \org.eclipse.jdt.debug.tests but other ones are not maintained in the project source...

On 09.06.2020 21:23, Gayan Perera wrote:
You will find information at https://www.vogella.com/tutorials/EclipsePlugin/article.html

Basically you need to create a Eclipse launch configuration with the plugins you have in workspace and run it. That will start a new eclipse instance with the plugin code that you have changed.

Br,
Gayan,

On Tue, Jun 9, 2020 at 8:50 PM Ari Kast <arikast@xxxxxxxxx> wrote:
Thanks for the responses, I ended up going the Oomph route, which worked -- I now have JDT imported into Eclipse (with no errors in the problems tab!).

But I'm not clear how the general build/test development cycle works.  Is there a way to run my jdt ui code changes within the same running Eclipse instance, or do I need to instead build an artifact, perhaps via cmd-line maven, and then run that artifact as a separate Eclipse instance to see the changes?  What's the actual development flow people use when writing code?

Thanks
Ari

On Fri, Jun 5, 2020 at 6:53 AM Gayan Perera <gayanper@xxxxxxxxx> wrote:
Try building like follows 

mvn -Pbuild-individual-bundles clean install

Br,
Gayan

On Thu, 4 Jun 2020 at 23:11, Ari Kast <arikast@xxxxxxxxx> wrote:
Hi 

I'm a developer looking to fix a few bugs of personal interest to me in eclipse.jdt.ui.

I don't understand how to build the project.  I cloned this repo git://git.eclipse.org/gitroot/platform/eclipse.platform.releng.aggregator.git

and followed its README instrux, which fail at this command:

    mvn clean verify  -DskipTests=true

which yields the error at bottom of this email. 

My questions:
1) how to build/run the project
2) are there general instructions for new devs like me?  I was following this https://wiki.eclipse.org/JDT_UI/How_to_Contribute#The_Build which didn't mention the aggregator pom at all, so maybe I'm building the wrong thing altogether?

Many thanks
Ari 

Here are the error details:

maven 3.6.3
MacOS 10.13.6
java version 1.8.0_162

Exception in thread "main" java.lang.AssertionError: pom file must not be null from PolyglotModelManager as per API
at org.sonatype.maven.polyglot.TeslaModelProcessor.locatePom(TeslaModelProcessor.java:65)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:457)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:398)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:362)
at org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:400)
at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:391)
at org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:78)
at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:511)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:221)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:955)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)


_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev

_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev

Back to the top