You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Brett Porter <br...@apache.org> on 2006/01/01 03:12:53 UTC
Re: Commons, Maven, Site, Release
Hi Dennis,
Thanks for trying this out. Sorry I left a couple of holes. I've
uploaded everything, and removed it locally, and verified it works.
The instructions are now:
- Download latest integration build from
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/ and
install per normal m2 instructions (the site will require Maven 2.0.2,
due for release in the next couple of weeks)
- run "mvn site" from trunks-sandbox
Let me know how it goes!
Cheers,
Brett
Dennis Lundberg wrote:
> Hi Brett
>
> I finally found some time to try out the new Maven 2 site stuff that
> you have put into the sandbox. There are quite a few hurdles to jump
> over though and I think I fell on the last one. Hope you can help me
> out. Here's what I did:
>
> - Bootstrapped Maven from the 2.0.x branch
>
> - Added to the sandbox pom.xml a build/plugins/plugin/version tag for
> maven-site-plugin and set it to 2.0-SNAPSHOT, to get all the fancy new
> stuff
>
> - Added a skin/version tag, with the value '1.0-SNAPSHOT' to
> src/site.xml, otherwise it tried to download the release version
>
> - Added snapshot repositories to the sandbox pom
>
> - When I run 'mvn site' in sandbox-trunks I get an error from Maven
> when it is trying to download the classic-skin, see stack trace below
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Commons, Maven, Site, Release
Posted by Dennis Lundberg <de...@mdh.se>.
Brett Porter wrote:
> Dennis Lundberg wrote:
>> Thanks for the quick response Brett. I have it all working now, thanks
>> to your changes.
>
> cool
>
>> To move this forward I have created a wiki page where anyone
>> interested can add their comments and experiences. For starters it
>> includes:
>
> thanks!
>
>> - basic steps to convert a component from Maven 1 to Maven 2
> I don't want to go too far down this path until we have a subset of
> sandbox components working 100%, but its great that you've started this.
> I'll try and keep it up to date :)
OK, I won't go there then...
> Some comments:
> * The copyright notice at the bottom is now right-aligned (before it was
> left-aligned) and a bit smaller than before
After some digging I found that it is the custom .jsl file in
commons-build that is responsible for the left-alignment.
That also explains why the size is different, because commons-build puts
a table inside the footer, which in turn contains the actual text.
> I'll file it in JIRA
See additional comments there.
> * There is no text "Doc for <version>" to the right of the publishing date
>
> I left that off the parent because it doesn't go on the parent
> site, but it should be in the subprojects. Add <version position="top"
> /> to site.xml
That needs to be <version position="left">, but yes it works nicely.
>> Learning by doing often works well for me, so I have converted
>> commons-id to Maven 2. At least the site generation is working
>> properly. But the unit tests are failing for me. Think I saw something
>> about that in another thread. Anyway, is there any interest in the
>> files that I have made for commons-id?
>>
> Since this doesn't interfere with existing builds, it'd be good to have
> another example. Have you put it into bugzilla?
Actually it does interfere. I have moved the xdocs from id/xdocs/ to
id/site/xdoc/. Will try to set the site root and see if it still works.
What is your opinion on directory-layout? Should we change it if/when
commons moves to Maven 2?
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Commons, Maven, Site, Release
Posted by Brett Porter <br...@apache.org>.
Dennis Lundberg wrote:
> Thanks for the quick response Brett. I have it all working now, thanks
> to your changes.
>
cool
> To move this forward I have created a wiki page where anyone
> interested can add their comments and experiences. For starters it
> includes:
thanks!
> - basic steps to convert a component from Maven 1 to Maven 2
I don't want to go too far down this path until we have a subset of
sandbox components working 100%, but its great that you've started this.
I'll try and keep it up to date :)
Some comments:
* The copyright notice at the bottom is now right-aligned (before it was
left-aligned) and a bit smaller than before
I'll file it in JIRA
* There is no text "Doc for <version>" to the right of the publishing date
I left that off the parent because it doesn't go on the parent
site, but it should be in the subprojects. Add <version position="top"
/> to site.xml
>
> Learning by doing often works well for me, so I have converted
> commons-id to Maven 2. At least the site generation is working
> properly. But the unit tests are failing for me. Think I saw something
> about that in another thread. Anyway, is there any interest in the
> files that I have made for commons-id?
>
Since this doesn't interfere with existing builds, it'd be good to have
another example. Have you put it into bugzilla?
Thanks,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Commons, Maven, Site, Release
Posted by Dennis Lundberg <de...@mdh.se>.
Thanks for the quick response Brett. I have it all working now, thanks
to your changes.
To move this forward I have created a wiki page where anyone interested
can add their comments and experiences. For starters it includes:
- instructions for getting started
- my experiences so far
- basic steps to convert a component from Maven 1 to Maven 2
If there are things that we feel needs to be changed in Maven we can add
references to the corresponding Jira issues.
The wiki page is here:
http://wiki.apache.org/jakarta-commons/CreatingSiteWithMaven2
Learning by doing often works well for me, so I have converted
commons-id to Maven 2. At least the site generation is working properly.
But the unit tests are failing for me. Think I saw something about that
in another thread. Anyway, is there any interest in the files that I
have made for commons-id?
--
Dennis Lundberg
Brett Porter wrote:
> Hi Dennis,
>
> Thanks for trying this out. Sorry I left a couple of holes. I've
> uploaded everything, and removed it locally, and verified it works.
>
> The instructions are now:
> - Download latest integration build from
> http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/ and
> install per normal m2 instructions (the site will require Maven 2.0.2,
> due for release in the next couple of weeks)
> - run "mvn site" from trunks-sandbox
>
> Let me know how it goes!
>
> Cheers,
> Brett
>
> Dennis Lundberg wrote:
>> Hi Brett
>>
>> I finally found some time to try out the new Maven 2 site stuff that
>> you have put into the sandbox. There are quite a few hurdles to jump
>> over though and I think I fell on the last one. Hope you can help me
>> out. Here's what I did:
>>
>> - Bootstrapped Maven from the 2.0.x branch
>>
>> - Added to the sandbox pom.xml a build/plugins/plugin/version tag for
>> maven-site-plugin and set it to 2.0-SNAPSHOT, to get all the fancy new
>> stuff
>>
>> - Added a skin/version tag, with the value '1.0-SNAPSHOT' to
>> src/site.xml, otherwise it tried to download the release version
>>
>> - Added snapshot repositories to the sandbox pom
>>
>> - When I run 'mvn site' in sandbox-trunks I get an error from Maven
>> when it is trying to download the classic-skin, see stack trace below
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org