If the XSD doesn't change until 1.1, I can live with it, although it would be nice to be able to validate my POMs.

However the documentation-patches in MAVEN-1410 also contains clarifications on how to create a proper POM and also clearly marks deprecated elements so that users don't start using them. I can remove the XSD-related documentation-changes and make a separate patch for the other enhancements. All I need to know is which branch to use.

--
Dennis Lundberg

Brett Porter wrote:
Right, I see.

I really didn't want to fudge around with the XSD for 1.0.x, and that will all
dealt with automatically in 1.1. I'll hold onto that issue for 1.1 to ensure it
does.

Cheers,
Brett

Quoting Dennis Lundberg <[EMAIL PROTECTED]>:


It seems that I had my issue-numbers mixed up. The changes I was refering to were the ones in MAVEN-1410, which is still open. With the change made to the documentation structure I don't think that the documentation-patch will apply. If I am going to redo the patches - should I make them against HEAD or one of the MAVEN-1_0_X branches?

--
Dennis Lundberg

Brett Porter wrote:

Sorry Dennis, those ended up on the mainline of CVS, then we switched back to the branch. The branch is now closed.

You should see the improvements within the next week.

- Brett

Dennis Lundberg wrote:


The site for Maven has been published, now that 1.0.1 is out the door. But I still don't see any of the documentation improvements that I made in MAVEN-1386 on the new site. Why is that? Is there anything I can do to get these improvements published?
--
Dennis Lundberg



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]







--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to