Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] Building EclipseLink

Andreas,

I'm not aware of any requirement for using Maven 3.0, I use 3.1, and expect 3.2 will work as well. I think the error messages are just different with the different versions. Though admittedly the 3.0 error reporting was more informative. 

As to why ant+maven and not just maven (or just ant)... the team opted for building the OSGi bundles manifest first, and the best tool found was Tycho. Since it is a maven plugin that also gave use another incentive to migrate from the old ant build. The build generates more than just OSGi bundles so we opted for a modular migration - the OSGi bundles were converted to maven first. Unfortunately the rest of the migration is running into unexpected hurdles...

No, there isn't a quick target to publish the built bundles to the local repo. part of the reason is intensional - tycho related use in combination with the rest of our build, I could throw together a command to publish to the local maven repo though if it is useful. The POMs are another matter. the build pom and the publish pom are different - to unify them I need to complete the migration, and as I mentioned I'm running into some problems.

2.5.1 should be at sonatype as well, when I get back from vacation I'll look into that as well.

Eric

On 2013-08-09, at 4:39 PM, Andreas Joseph Krogh <andreak@xxxxxxxxxxxx> wrote:

På fredag 09. august 2013 kl. 22:25:57, skrev Andreas Joseph Krogh <andreak@xxxxxxxxxxxx>:
På fredag 09. august 2013 kl. 18:53:06, skrev Eric Gwin <eric.gwin@xxxxxxxxxx>:
Andreas,

You need ant, maven, and java installed. then run from your trunk dir "ant -f antbuild.xml" should start the build. the ant build will call maven. it may stop after the maven build with a "no bnd" error. (I'll be fixing that when I return on Monday.), but by then the bundles will all have been built and should be available in the plugins dir.

I think 2.5 should be available on the sonatype OSS and eclipse maven sites (vacation brain - I'll verify and let you know).
 
Thanks, it was the "ant -f antbuild.xml" part I was missing. Is that information available somewhere?
 
Juse curious; Why isn't EL using Maven, and not Ant, when Maven is used by Ant?
 
I know 2.5 is available at sonatype, but I was wondering about 2.5.1-SNAPSHOT builds, are they anywhere?
 
Anyway, thanks for the info, I'm building EL now to test the converter-fixes.
 
Oh, the build just barfed (I'm using Maven-3.1) with:
 
     [java] Exception in thread "main" java.lang.NoSuchMethodError: org.apache.maven.execution.MavenSession.getRepositorySession()Lorg/sonatype/aether/RepositorySystemSession;
     [java]     at org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:92)
     [java]     at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:144)
     [java]     at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.setupProjects(P2TargetPlatformResolver.java:126)
     [java]     at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:87)
     [java]     at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:77)
     [java]     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
     [java]     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
     [java]     at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
     [java]     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
     [java]     at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
     [java]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     [java]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
     [java]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     [java]     at java.lang.reflect.Method.invoke(Method.java:606)
     [java]     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
     [java]     at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
     [java]     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414)
     [java]     at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
BUILD FAILED
/home/andreak/dev/eclipselink.runtime/antbuild.xml:341: Java returned: 1
 
I guess I have to bild with Maven-3.0 and not 3.1...
 
Yep, it build with Maven-3.0.5 and failes (as you said) with:
 
BUILD FAILED
/home/andreak/dev/eclipselink.runtime/antbuild.xml:372: The following error occurred while executing this line:
/home/andreak/dev/eclipselink.runtime/utils/org.eclipse.persistence.dbws.builder/antbuild.xml:206: Missing BND library!
 
I see, as you said, lots of jars in plugins/ but no poms. Is there a magic command to issue for having the generated jars, with poms and deps deployed to my local $HOME/.m2/repository/ ?
 
Thanks.
 
--
Andreas Joseph Krogh <andreak@xxxxxxxxxxxx>      mob: +47 909 56 963
Senior Software Developer / CTO - OfficeNet AS - http://www.officenet.no
Public key: http://home.officenet.no/~andreak/public_key.asc
 
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users


Back to the top