Well the support Forum of l2umbrella isnt the most active forum, and i need my server back up fast so i ask here ^^
Well i used a tutorial, and nearly everything worked fine, i got the l2loginserver-dist.zip in the loginserver target folder but not the gameserver zip in gameserver target folder =( could you help me? I 100% used this tutorial (just edited the names and links to ur svn) :
[iNFO] Scanning for projects...
[iNFO] ------------------------------------------------------------------------
[iNFO] Building Unnamed - l2jfree:l2j-gameserver:jar:1.0.0
[iNFO]
[iNFO] Id: l2jfree:l2j-gameserver:jar:1.0.0
[iNFO] task-segment: [assembly:assembly] (aggregator-style)
[iNFO] ------------------------------------------------------------------------
[iNFO] [statemgmt:start-fork]
[iNFO] Starting forked execution [fork id: 729154200]
[iNFO] [buildnumber:create]
[iNFO] Storing buildNumber: 929
[iNFO] [resources:resources]
[iNFO] Using default encoding to copy filtered resources.
[iNFO] [compiler:compile]
[iNFO] Compiling 1429 source files to C:\Dokumente und Einstellungen\Elke the sheep\workspace\L2_UmbrellaGS_CT1.5\target\classes
[ERROR]
Mojo (aggregator):
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
FAILED while executing in directory:
C:\Dokumente und Einstellungen\Elke the sheep\workspace\L2_UmbrellaGS_CT1.5
Reason:
Failure executing javac, but could not parse the error:
The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: Java heap space
at com.sun.tools.javac.comp.MemberEnter.signature(MemberEnter.java:365)
at com.sun.tools.javac.comp.MemberEnter.visitMethodDef(MemberEnter.java:560)
at com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:639)
at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387)
at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:399)
at com.sun.tools.javac.comp.MemberEnter.finishClass(MemberEnter.java:410)
at com.sun.tools.javac.comp.MemberEnter.finish(MemberEnter.java:1000)
at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:967)
at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386)
at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758)
at com.sun.tools.javac.comp.Enter.complete(Enter.java:451)
at com.sun.tools.javac.comp.Enter.main(Enter.java:429)
at com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727)
at com.sun.tools.javac.main.Main.compile(Main.java:353)
at com.sun.tools.javac.main.Main.compile(Main.java:279)
at com.sun.tools.javac.main.Main.compile(Main.java:270)
at com.sun.tools.javac.Main.compile(Main.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)
at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:180)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
[iNFO] ------------------------------------------------------------------------
[iNFO] For more information, run with the -e flag
[iNFO] ------------------------------------------------------------------------
[iNFO] BUILD FAILED
[iNFO] ------------------------------------------------------------------------
[iNFO] Total time: 19 seconds
[iNFO] Finished at: Wed Jul 16 12:41:57 CEST 2008
[iNFO] Final Memory: 13M/60M
[iNFO] ------------------------------------------------------------------------
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
The heavy lifting is done in the client, because while you can get away with small imperfections in the java, everything in the client must be impecable.
So, if you haven't touched the client, I'd say pick the newest protocol version you can find the client editing tools and Interface.u (mandatory) / NWindow.dll (better to have it) / Engine.dll (optional) sources for.
At the very least, you need the Interface.u to fix the Clan Window and enable skill enchanting on Classic/Essence versions, if you decide to use one of them instead of MAIN/LIVE.
Thanks for clarification. Do you think the newest clients offer solid advantages compared to the classic ones like Salvation?
I'm also in the process of porting h5 to one of them just for the sake of it, so I was wondering if I should just attempt to go to the newest possible.
Upgrading to Salvation is exactly the same as upgrading to the newest client with the only difference being access to free-shared client editing tools and resources.
I am speaking from experience. I have upgraded my HF source to one of the newest clients by myself (in terms of server side. got help with the client) and hit every single wall there was in the process.
Now, I already have several multi-protocool server cores so I can easily compare different approaches to tackling the same issue, which also helped the learning process.
Best way to learn would be to use this one (link below) to snoop around and figure out what has been changed in the server side (the packet structure will be different, for sure, but works for understanding/figuring the process out in general terms).
https://github.com/iBezneR/L2J_SunriseProject_Purity
The client side will always be the same, always the same files, only the DAT structure will be different. I personally wrote myself some parsers for the data of the DAT files from OLD -> NEW client.
I guess if you want to learn the whole process, your best bet is to start with a classic client (like salvation? also must be easy to modify so that you don't get stuck behind paywalls) and check how the network communication is implemented. L2jmobius has a lot of sources that use classic clients.
Question
Dethroned
Well the support Forum of l2umbrella isnt the most active forum, and i need my server back up fast so i ask here ^^
Well i used a tutorial, and nearly everything worked fine, i got the l2loginserver-dist.zip in the loginserver target folder but not the gameserver zip in gameserver target folder =( could you help me? I 100% used this tutorial (just edited the names and links to ur svn) :
http://www.maxcheaters.com/forum/index.php?topic=25422.0
This is the log of doing maven build:
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.