Build failing
wilfred
out that I dropped the snapshot repository currently hosting the maven-
it-helper dependency required for running the integration tests. I
added the snapshot repository back in, so everything is fine now.
(On the plus side: this issue was tracked using our new JIRA support:
http://kenai.com/jira/browse/SPRINGME-1; first issue closed!)
Wilfred Springer
Hmmm, that's weird. It's working fine on my system. Thinking...
Could you send me the output?
If the build is breaking, that could be because of some changes that I
made lately. Preparing my talk on Spring ME next week on Wednesday. I
will to look into it soon. But you will definitely have a snapshot
build next week.
Wilfred
On Apr 11, 2009, at 9:08 PM, stevez wrote:
> Hi, wilfred,
>
> Today I just found springme project from a website, it is quite
> intersting for me, because I've been looking the DI solution in J2ME
> for a long time.
> I can feel this is very excellent project for mobile developers.
>
> I download the source code and try to build it, but I failed.
>
> All the codes are downloaded from http://springme.sourceforge.net/,
> but I could not find the snapshot builds.
>
> I need a build and hope it could be tested on the real j2me device.
>
> Could you explain to me how to build your framework step by step?
>
> The maven tool I used is maven 2.1.0.
>
> Thanks
>
> steve
stevez
Thanks for your reply.
First I realized I did not check out the whole source code, because I
only find the three folders in your website: springme.sourceforge.net,
I just found your project in here: http://sourceforge.net/projects/springme/
Then I found the whole trunk of the source code. you should put all
your code information on your website, it is confusing.
This time it is much better, but it still build failed.
Following are the steps I did:
1. in trunk folder, I just type mvn clean, it complains 1 snapshot
file is missing.
2. then I type mvn install, it has the following error message:
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) javassist:javassist:jar:3.3.GA
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=javassist -
DartifactId=javassist -Dvers
ion=3.3.GA -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the
file there:
mvn deploy:deploy-file -DgroupId=javassist -
DartifactId=javassist -Dversio
n=3.3.GA -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -
DrepositoryId=[id]
Path to dependency:
1) me.springframework:spring-me-core:jar:1.0-SNAPSHOT
2) javassist:javassist:jar:3.3.GA
----------
1 required artifact is missing.
for artifact:
me.springframework:spring-me-core:jar:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1 minute 24 seconds
[INFO] Finished at: Sat Apr 11 18:34:11 EDT 2009
[INFO] Final Memory: 25M/48M
[INFO]
------------------------------------------------------------------------
D:\dev\springMe\springme\trunk>
What does it mean, does it mean it needs javaassist or the plugin
snapshot?
Thanks
steve
On Apr 11, 4:05 pm, Wilfred Springer <wilfredsprin...@gmail.com>
wrote:
>
> Hmmm, that's weird. It's working fine on my system. Thinking...
>
> Could you send me the output?
>
> If the build is breaking, that could be because of some changes that I
> made lately. Preparing my talk on Spring ME next week on Wednesday. I
> will to look into it soon. But you will definitely have a snapshot
> build next week.
>
> Wilfred
>
> On Apr 11, 2009, at 9:08 PM, stevez wrote:
>
> > Hi, wilfred,
>
> > Today I just found springme project from a website, it is quite
> > intersting for me, because I've been looking the DI solution in J2ME
> > for a long time.
> > I can feel this is very excellent project for mobile developers.
>
> > I download the source code and try to build it, but I failed.
>
Wilfred Springer
I was thinking about using Javassist for testing the generated output.
Never mind. I will remove it altogether. In fact, I just did it.
As for the confusing sub-projects. This is just the generated Maven
site, and what you find there is typical what you would normally find
on Maven site. In a multi-module project, you would typically find the
root project at the top, and if you navigate to the source code page
for that project, then there is a page for checking out the entire
project, like here: http://springframework.me/source-repository.html
I will probably upload a new version of the site to the
springframework.me (=springme.sourceforge.net) one of these days.
Wilfred
Wilfred Springer
I fixed the Maven dependency version. Hopefully everything works out
fine on your system next time you do a build.
Wilfred
On Apr 12, 2009, at 12:54 AM, stevez wrote:
> Hi, wilfred,
>
> After I downloaded and installed the javaassist-3.3-GA.jar,
>
> It has another error message:
>
> D:\dev\springMe\springme\trunk>mvn install:install-file -
> DgroupId=javassist -Dar
> tifactId=javassist -Dversion=3.3.GA -Dpackaging=jar -Dfile= ..
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Spring ME
> [INFO] Spring ME API
> [INFO] Spring ME Core
> [INFO] Spring ME Maven Plugin
> [INFO] Spring ME Integration Tests
> [INFO] Spring ME GWT Sample
> [INFO] Spring ME Samples
> [INFO] Spring ME Sample (Movie API)
> [INFO] Spring ME Sample Java ME
> [INFO] Spring ME Sample Commandline
> [INFO] Spring ME Adapter
> [WARNING] POM for 'com.agilejava.docbkx:docbkx-maven-plugin:pom:2.0.9'
> is invali
> d.
>
> Its dependencies (if any) will NOT be available to the current build.
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
>
>
> Project ID: com.agilejava.docbkx:docbkx-maven-plugin
> POM Location: Artifact [com.agilejava.docbkx:docbkx-maven-plugin:pom:
> 2.0.9]
> Validation Messages:
>
> [0] 'dependencies.dependency.version' is missing for
> com.agilejava.docbkx:d
> ocbkx-maven-base
>
>
> Reason: Failed to validate POM for project
> com.agilejava.docbkx:docbkx-
> maven-plu
> gin at Artifact [com.agilejava.docbkx:docbkx-maven-plugin:pom:2.0.9]
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Sat Apr 11 18:51:21 EDT 2009
> [INFO] Final Memory: 2M/4M
> [INFO]
> ------------------------------------------------------------------------
> D:\dev\springMe\springme\trunk>
>
>
> On Apr 11, 4:05 pm, Wilfred Springer <wilfredsprin...@gmail.com>
> wrote:
>> Hi Steve,
>>
>> Hmmm, that's weird. It's working fine on my system. Thinking...
>>
>> Could you send me the output?
>>
>> If the build is breaking, that could be because of some changes
>> that I
>> made lately. Preparing my talk on Spring ME next week on Wednesday. I
>> will to look into it soon. But you will definitely have a snapshot
>> build next week.
>>
>> Wilfred
>>
>> On Apr 11, 2009, at 9:08 PM, stevez wrote:
>>
>>> Hi, wilfred,
>>
>>> Today I just found springme project from a website, it is quite
>>> intersting for me, because I've been looking the DI solution in J2ME
>>> for a long time.
>>> I can feel this is very excellent project for mobile developers.
>>
>>> I download the source code and try to build it, but I failed.
>>
>>> All the codes are downloaded fromhttp://springme.sourceforge.net/,
stevez
I will try to check out the new source code later.
Following are my new finding:
1. Now I can build the whole project using command line, but there are
some issues when I build inside the eclipse.
2. When I run mvn test, all the I shows test successfully, but I found
0 case is tested.
3. I try to run the J2ME midlet on the wireless toolkit emulator, but
it failed, I know you use microemulator 2.0.3 as libray to build the
j2ME app, which is actually a J2SE application, could you tell me how
to build a real j2ME application, or could you implement the build
script into your maven script?
4. When I tried run the mvn site at trunk folder, it failed again:
[INFO] [docbkx-fop-support:generate {execution: default}]
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] basedir D:\Users\wilfred\Library\Fonts does not exist
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalStateException: basedir D:\Users\wilfred\Library
\Fonts does not
exist
at org.codehaus.plexus.util.DirectoryScanner.scan
(DirectoryScanner.java:
542)
at
com.agilejava.docbkx.support.fop.FontmetricsMojo.getFontFiles(Fontmet
ricsMojo.java:124)
at com.agilejava.docbkx.support.fop.FontmetricsMojo.execute
(FontmetricsM
ojo.java:63)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPlugi
nManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLi
fecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced
(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode
(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 38 seconds
[INFO] Finished at: Sun Apr 12 14:25:35 EDT 2009
[INFO] Final Memory: 10M/19M
------------------------------------------------------------------------
D:\dev\springMe\springme\trunk>
Steve
On Apr 12, 2:00 pm, Wilfred Springer <wilfredsprin...@gmail.com>
stevez
I checked out the new source, and this time it is much better.
But there is still an issue in building the spring-me-sample-cmdline,
it requires
args4j-2.0.11.jar
After I manually install it under the spring-me-sample-cmdline folder,
it is OK.
I found when I install it under the trunk folder, it always threw an
error.
And I still don't know how to run the generated J2ME ample jad and jar
file on the J2ME emulator.
Thanks
steve
On Apr 12, 2:00 pm, Wilfred Springer <wilfredsprin...@gmail.com>
Wilfred Springer
I ran the Midlet on Microemulator and the MPP SDK. Since I am on Mac,
I don't have access to the Wireless Toolkit.
Args4j is only on the dev.java.net repository, so I guess I already
had that one installed before. I will add the dev.java.net repository
as a repository to the pom.
For using Eclipse, what I do is just run mvn eclipse:eclipse, and I
get all of the Eclipse files for free.
The Midlet is just an example. We used Spring ME to build a Java ME
based navigation application at TomTom, so it should all be working
fine. ;-)
BTW, I will be offline for the next day and a half.
Wilfred
On Apr 12, 2009, at 9:22 PM, stevez wrote:
>
> Hi, wilfred,
>
wilfred
the problem. It turned out it was a j2me-maven-plugin issue. It's now
running both on my phone, as well as WTK.
stevez
I checked out the new source code.
This time the generated jad and jar file work on my WTK emulator. The
app is too simple, but it works anyway.
But I found I have to run mvn clean under the folder spring-me-samples
first, or it will fail.
Thanks, wilfred!