It finally worked fine when I did "mvn install"   (If I added
-Dmaven.test.skip=true)

But when I am trying to create a tomcat war-file it fails

  cd weblogger-war-assembly
  mvn -Dtomcat=true install
  cd ..

  cd weblogger-assembly
  mvn -Dtomcat=true install
  cd ..

And the .war-file in roller-weblogger-5.0.0-RC4-for-tomcat.zip is
almost empty (Only a MANIFEST file)

/Susanne







2011/2/9 David Johnson <[email protected]>:
> On Feb 9, 2011, at 11:27 AM, Susanne Gladén wrote:
>> Ok. So now I have tried this as well.
>>
>> I have svn and maven installed:
>> svn, version 1.6.15 (r1038135)   compiled Dec 17 2010, 09:05:59
>> Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100)
>> Java version: 1.6.0_23
>>
>> I checked out the source code from trunk and then I did mvn eclipse:eclipse
>
> I'm not sure what "mvn eclipse:eclipse" is supposed to do.
> To build Roller all you should need is "mvn install"
> What happened when you tried that on the pom.xml file?
>
> - Dave
>
>
>
>>
>> It failed:
>>
>> [INFO] Resource directory's path matches an existing source directory.
>> Resources will be merged with the source directory src/main/resources
>> [INFO] 
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO] 
>> ------------------------------------------------------------------------
>> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
>> src
>> /main/resources: output=target/classes, include=[org/**], 
>> exclude=[**/sql/**|**/
>> *.java], test=false, filtering=false, merging with=resource 
>> src/main/resources:
>> output=target/classes, include=[roller-version.properties|META-INF/**], 
>> exclude=
>> [**/*.java], test=false, filtering=true
>> [INFO] 
>> ------------------------------------------------------------------------
>> [INFO] For more information, run Maven with the -e switch
>> [INFO] 
>> ------------------------------------------------------------------------
>> [INFO] Total time: 5 seconds
>> [INFO] Finished at: Wed Feb 09 17:23:45 CET 2011
>> [INFO] Final Memory: 18M/44M
>> [INFO] 
>> ------------------------------------------------------------------------
>>
>>
>> Also I got several:
>> Sources for some artifacts are not available.
>> Javadoc for some artifacts are not available.
>>
>> /Susanne
>>
>>
>>
>> 2011/2/9 shelan Perera <[email protected]>:
>>> Hi Susanne,
>>>
>>> I would like to add some thoughts for the build process (This is what i use/
>>> prefer so a suggestion to try out :)..).I prefer use command line to build
>>> rather than IDE.( I use IDE to view and edit code mainly.)
>>>
>>> This is the command line process that i follow.
>>>
>>> make sure you have Maven and Subversion installed.
>>>
>>> type svn --version to check if it is not installed you have to install and
>>> set the environment variables first.
>>>
>>> issue comand svn co
>>> https://svn.apache.org/repos/asf/roller/trunkroller_trunk to
>>> get the latest source from trunk.
>>>
>>> once you have checked out the source you can create an eclipse compatible
>>> project using
>>>
>>> mvn eclipse:eclipse
>>>
>>> It will generate project files so you can open the project using
>>> File-->Import--->Existing project into workspace.
>>>
>>> you can build the sources navigating to the file in command line and issuing
>>> command
>>>
>>> mvn clean install
>>>
>>> to run the web app navigate to weblogger-webapp and then issue
>>>
>>> mvn jetty:run
>>>
>>> You can tests the roller at
>>> http://localhost:8080/roller
>>>
>>>
>>> Hope this will help you.Once this is done you can confidently try to
>>> integrate with Eclipse.
>>>
>>> Thanks
>>>
>>>
>>>
>>> On Wed, Feb 9, 2011 at 6:44 PM, Susanne Gladén 
>>> <[email protected]>wrote:
>>>
>>>> Hi,
>>>>
>>>> I got these errors when eclipse auto-built. This happened after I
>>>> imported the maven projects.
>>>>
>>>> I now ran maven clean and then maven install and I got
>>>> "javac is not an internal command"    (How can I fix this in eclipse?
>>>> I dont want to change the env. variable path)
>>>>
>>>> I then set the global env variable PATH to %PATH%;.....jdk/bin
>>>>
>>>> Then maven clean -> maven install again
>>>>
>>>> Now I get that "svn is not an internal command"
>>>>
>>>> If I open cmd and run svn --version I get "svn is not an internal command"
>>>> Shouldnt it be enough to have installed subversion?
>>>>
>>>> /Susanne
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 2011/2/9 Dave <[email protected]>:
>>>>> Hi Susanne,
>>>>>
>>>>> Thanks for writing up the problem(s).
>>>>>
>>>>>
>>>>> On Wed, Feb 9, 2011 at 3:20 AM, Susanne Gladén <[email protected]>
>>>> wrote:
>>>>>> I now checked out the code from trunk and I followed the steps in:
>>>>>>
>>>> https://cwiki.apache.org/confluence/display/ROLLER/Build+and+Run+Roller+5+in+Eclipse
>>>>>
>>>>> I just wrote those instructions last week, so you may be the first
>>>>> "tester" here. They work for me, but until they work for others they
>>>>> are useless so let's fix them.
>>>>>
>>>>>
>>>>>> When building I get the following errors:
>>>>>
>>>>> What steps are you on in the process here? What did you use to invoke
>>>>> the build? You should first run "mvn install" on the pom.xml file at
>>>>> the top of the Roller trunk directory.
>>>>>
>>>>>> Build errors for roller-planet-business;
>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>> execute goal org.apache.maven.plugins:maven-antrun-plugin:1.2:run
>>>>>> (gen-db-scripts) on project roller-planet-business: Execution
>>>>>> gen-db-scripts of goal
>>>>>> org.apache.maven.plugins:maven-antrun-plugin:1.2:run failed: Plugin
>>>>>> org.apache.maven.plugins:maven-antrun-plugin:1.2 or one of its
>>>>>> dependencies could not be resolved: Could not find artifact
>>>>>> org.apache.roller:test-utils:jar:5.0.0-RC4 in central
>>>>>> (http://repo1.maven.org/maven2)
>>>>>
>>>>> Here, it appears that the test-utils jar was not built for some
>>>>> reason. This might be happening because of the way you launched the
>>>>> build, or the failure below.
>>>>>
>>>>>
>>>>>> Build errors for roller-weblogger-business;
>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>> execute goal
>>>> org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-3:create
>>>>>> (default) on project roller-weblogger-business: Cannot get the
>>>>>> revision information from the scm repository : Error!
>>>>>
>>>>> Here it seems the build cannot connect to SVN to determine the
>>>>> revision number to put into the build. I'm not sure what could cause
>>>>> that because you said that you have Subclipse and therefore the
>>>>> Subversion client installed.
>>>>>
>>>>> To fix this you may have to install a Subversion client separately
>>>>> from Eclipse. Or maybe you already have one? Open up a command-line
>>>>> window and run "svn --version" and tell us what you get.
>>>>>
>>>>> The rest of the errors are due to test-utils not being built.
>>>>>
>>>>> Hope that helps,
>>>>>
>>>>> - Dave
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Shelan Perera
>>>
>>> Home: http://www.shelan.org
>>> Blog   : http://www.shelanlk.com
>>> Twitter: shelan
>>> skype  :shelan.perera
>>> gtalk   :shelanrc
>>>
>>>  I am the master of my fate:
>>>  I am the captain of my soul.
>>>         *invictus*
>>>
>
>

Reply via email to