Hi Ulrich,
Excellent. I tested here and it works with a few workarounds (Probably
because I'm using Windows). For example:
1) I have to define the maven.localRepository.baseDir by hand in command
line. I don't know why, but maven is eliminating backslashes "\" from
the given path.
2) I have to modify the code of PackageMojo.java and uncomment the line:
String fileName = /*this.getProjectFolder()*/ +
this.getArtifactFileName();
Maven cannot find the artifact file using relative path.
As wobootstrap don't generate pom.xml for installed libraries, maven try
to download it and fail with warnings for each webobjects jar. It's not
a problem, but it is annoying. A simple solution is to add the following
into the constructor of BootstrapMojo.java causing install:install-file
to generate a simple pom.xml for each webobjects jar:
installFileProperties.setProperty( "generatePom", "true" );
This solution is only a workaround, since it's not declaring the
transitive dependencies related with each jar.
Cheers,
Henrique
Ulrich Köster wrote:
> Here we go:
>
> prepare:
> - download and install maven 2.0.4 http://maven.apache.org
> - download the settings.xml and
> examples.tar http://objectstyle.org/confluence/display/WOL/WOProject-Maven2
> (links are at the bottom of the page)
> - cp the settings.xml to ~.m2/settings.xml
>
> install the maven plugin:
> - checkout the latest woproject
> - invoke 'mvn install' (at the same location where you usually invoke ant)
>
> example:
> - cd into the MavenHelloWorldDependency project
> - ivoke 'mvn woproject:bootstrap' this step is required once to get
> apples jars into the repository
> - invoke 'mvn install'
> - cd into the MavenHelloWorld project
> - invoke 'mvn install'
>
> You will find the woa and framework in the repository under
> ~.m2/repository/org/objectstyle/woproject/maven2/examples/
>
> Difference between a wo pom.xml and a standard pom.xml:
>
> The packaging is
> either <packaging>woframework</packaging> or <packaging>woapplication</packaging>.
>
> Include the extensions in the build:
>
>
> <build>
> ....
> <plugins>
> <plugin><!-- required to overwrite the package lifecyle -->
> <groupId>org.objectstyle.woproject.maven2</groupId>
> <artifactId>maven-woproject-plugin</artifactId>
> <version>2.0-SNAPSHOT</version>
> <extensions>true</extensions>
> </plugin>
> </plugins>
> ...
> </build>
>
> uli
>
> Am 20.10.2006 um 16:23 schrieb Mike Schrag:
>
>> Thanks -- No rush ...
>>
>> On Oct 20, 2006, at 9:36 AM, Ulrich Köster wrote:
>>
>>> For sure. Give me some days.
>>>
>>> Uli
>>> Am 18.10.2006 um 22:13 schrieb Mike Schrag:
>>>
>>>> Hey Ulrich .. I've never used Maven and Anjo and I have been talking
>>>> about the build system in Project Wonder. I feel like I should take
>>>> a look at Maven if we're going to do something with it. I was
>>>> wondering if you happen to have an example WO app and/or framework
>>>> built with it that you might be willing to send me to see just how
>>>> the heck it works?
>>>>
>>>> ms
>>>
>>
>
--\o/ Henrique Prange, Moleque de Idéias Educaçăo e Tecnologia Ltda | Phone: 55-21-2710-0178 E-mail: hprang..oleque.com.br / \ http://www.moleque.com.br
This archive was generated by hypermail 2.0.0 : Sun Oct 29 2006 - 13:36:35 EST