... and of course here comes the follow-up: version 19 is out.
Provides a fix for the belatedly discovered 
http://jira.magnolia-cms.com/browse/BUILD-57

Sorry for the inconvenience,

-greg

On Nov 24, 2010, at 13:35, Grégory Joseph wrote:

> 
> Hi list,
> 
> We just release new version of our parent POMs. Transition from -17 should be 
> transparent, but there are a bunch of changes.
> 
> First and foremost, the introduction of a parent pom for Forge projects. 
> Forge project leads: the usage of this parent pom is not mandatory *at all*. 
> It's merely provided as a convenience... if it IS convenient for you, that 
> is. Please send feedback my way for ideas or improvements!
> 
> Arbitrary selection of other new "features":
> * Hudson should now systematically generate and deploy source and test-source 
> jars for all projects
> * Fix "simple" bundles so they don't need to use the jar packaging - i.e no 
> "empty" jars
> * Fixed Javadoc linking, which was erroneously linking to 
> www.magnolia-cms.com in some places
> * Enable embedding of Clover license in settings.xml (our internal 
> settings.xml template has such a license, no more need to email a license 
> file)
> * Improvements and cleanup of generated README files
> * Updated a bunch of plugins and reports
> 
> For details, see:
>  
> http://jira.magnolia-cms.com/secure/ReleaseNote.jspa?projectId=10330&version=11641
> 
> Please let me know if you encounter any difficulty in updating your project - 
> or using these parent poms at all - as well as any idea or need for 
> improvement you might have.
> 
> Cheers,
> 
> -greg
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to