« Return to Thread: Preparing the Pluto Release
Re: Preparing the Pluto Release
by Ate Douma
::
Rate this Message:
Hi Carsten,
Build should be working again I think. I just committed some testsuite/pom.xml fixes restoring maven-war-plugin and maven-plugin-plugin
configurations which were lost somehow.
In addition, I've added a maven-remote-resources-plugin fix to correct where the legal files are put. With that fix the override of the
ianal-maven-plugin isn't needed anymore.
I haven't had time to review the other changes to the build yet (will do so shortly), possibly the above might also apply there.
Ate
Carsten Ziegeler wrote:
> Ate Douma wrote:
>> Carsten Ziegeler wrote:
>>> Hi,
>>>
>>> I've cleaned up current trunk in order to make the release (hopefully)
>>> easier. But unfortunately I ran into problems (see below).
>>>
>>> The idea is to release the separate modules as maven artifacts (in
>>> binary form with attached source, javadocs artifacts), a big source
>>> release of the whole pluto trunk and for convenience a binary version of
>>> Pluto containing Tomcat.
>>>
>>> While the first two seem to work now (I also ran the RAT profile), the
>>> last one is giving me some problems as I don't understand at all how
>>> this is supposed to work :)
>>> There is the ant file doing all the magic, the ant file itself starts
>>> maven to build the whole project. It also uses the maven pluto plugin to
>>> install the war files (portal and testsuite) but for some reason the
>>> testsuite war file doesn't get rewritten. Unfortunately does neither the
>>> util code nor the plugin itself have any log output. I think as soon as
>>> we have fixed this rewriting, we are ready for release.
>>>
>>> Does anyone have a good clue? (I'll need to do a break for some hours,
>>> if not I guess I have to debug the maven plugin).
>> Hi Carsten,
>>
>> No, I don't have a good clue yet.
>> But I can try to look at it too.
>> Can you post the exact command(s) you're running so I can replay myself?
>>
> Hi Ate,
>
> great, I'm just doing an
> "ant -f dist-build.xml" in the root dir; this downloads tomcat, builds
> everything and creates a dist under target/dist.
> The dist itself looks good, apart from the fact that testsuite is not
> rewritten for pluto.
> So I invoked the pluto maven plugin directly in the testsuite module:
> mvn org.apache.portals.pluto:maven-pluto-plugin:2.0.0-SNAPSHOT:install
> -DinstallDir={PATH to the /target/dist/apache-tomcat-6.0.18 dir}
>
> This copies over the webapp to the tomcat dir (/PlutoDomain sub dir),
> but the resulting war is not rewritten.
>
> Regards
> Carsten
Build should be working again I think. I just committed some testsuite/pom.xml fixes restoring maven-war-plugin and maven-plugin-plugin
configurations which were lost somehow.
In addition, I've added a maven-remote-resources-plugin fix to correct where the legal files are put. With that fix the override of the
ianal-maven-plugin isn't needed anymore.
I haven't had time to review the other changes to the build yet (will do so shortly), possibly the above might also apply there.
Ate
Carsten Ziegeler wrote:
> Ate Douma wrote:
>> Carsten Ziegeler wrote:
>>> Hi,
>>>
>>> I've cleaned up current trunk in order to make the release (hopefully)
>>> easier. But unfortunately I ran into problems (see below).
>>>
>>> The idea is to release the separate modules as maven artifacts (in
>>> binary form with attached source, javadocs artifacts), a big source
>>> release of the whole pluto trunk and for convenience a binary version of
>>> Pluto containing Tomcat.
>>>
>>> While the first two seem to work now (I also ran the RAT profile), the
>>> last one is giving me some problems as I don't understand at all how
>>> this is supposed to work :)
>>> There is the ant file doing all the magic, the ant file itself starts
>>> maven to build the whole project. It also uses the maven pluto plugin to
>>> install the war files (portal and testsuite) but for some reason the
>>> testsuite war file doesn't get rewritten. Unfortunately does neither the
>>> util code nor the plugin itself have any log output. I think as soon as
>>> we have fixed this rewriting, we are ready for release.
>>>
>>> Does anyone have a good clue? (I'll need to do a break for some hours,
>>> if not I guess I have to debug the maven plugin).
>> Hi Carsten,
>>
>> No, I don't have a good clue yet.
>> But I can try to look at it too.
>> Can you post the exact command(s) you're running so I can replay myself?
>>
> Hi Ate,
>
> great, I'm just doing an
> "ant -f dist-build.xml" in the root dir; this downloads tomcat, builds
> everything and creates a dist under target/dist.
> The dist itself looks good, apart from the fact that testsuite is not
> rewritten for pluto.
> So I invoked the pluto maven plugin directly in the testsuite module:
> mvn org.apache.portals.pluto:maven-pluto-plugin:2.0.0-SNAPSHOT:install
> -DinstallDir={PATH to the /target/dist/apache-tomcat-6.0.18 dir}
>
> This copies over the webapp to the tomcat dir (/PlutoDomain sub dir),
> but the resulting war is not rewritten.
>
> Regards
> Carsten
« Return to Thread: Preparing the Pluto Release
| Free embeddable forum powered by Nabble | Forum Help |
