site nav, style as artifacts? new POM elements?

Hi, I'm thinking about the situation where you have a number of projects in a group, with an independantly buildable site that shares common elements with a parent project. What about having the navigation and anything along the lines of site.jsl or whatever would be used in m2 as artifacts tha

[jira] Updated: (MAVEN-1501) maven seems not to evaluate .properties of parent pom

The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Fri, 12 Nov 2004 5:33 PM Changes: assignee changed to Brett Porter description changed from My pop extends an other pom. ../../project-defaults.xml In th

[jira] Commented: (MAVEN-1501) maven seems not to evaluate .properties of parent pom

The following comment has been added to this issue: Author: Brett Porter Created: Fri, 12 Nov 2004 5:28 PM Body: this is a regression resulting from fixing >1 level of inheritence. It only fails for build in properties (most importantly, maven.repo.remote). -

cvs commit: maven-plugins/plugin-parent project.properties

brett 2004/11/12 14:03:23 Modified:plugin-parent project.properties Log: set compile source/target Revision ChangesPath 1.14 +5 -0 maven-plugins/plugin-parent/project.properties Index: project.properties =

Re: The newly generated site for Maven

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 an

[jira] Updated: (MPLINKCHECK-17) Unsupported major.minor version 48.0

The following issue has been updated: Updater: Carlos Sanchez (mailto:[EMAIL PROTECTED]) Date: Fri, 12 Nov 2004 4:45 PM Comment: Confirmed, it was compiled with source=1.4 Changes: assignee changed to Carlos Sanchez Fix Version changed to 1.3.4

The newly generated site for Maven

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 -

[jira] Created: (MPLINKCHECK-17) Unsupported major.minor version 48.0

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPLINKCHECK-17 Here is an overview of the issue: -

[jira] Created: (MAVEN-1501) maven seems not to evaluate .properties of parent pom

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1501 Here is an overview of the issue: - Key:

cvs commit: maven/xdocs/misc glossary.xml

brett 2004/11/12 04:42:52 Modified:xdocs/misc glossary.xml Log: add link Revision ChangesPath 1.4 +1 -1 maven/xdocs/misc/glossary.xml Index: glossary.xml === RCS file: /home/cvs/maven/xd

cvs commit: maven/xdocs index.xml navigation-pdf.xml navigation.xml

brett 2004/11/12 04:41:53 Modified:xdocsindex.xml navigation-pdf.xml navigation.xml Log: fix some links Revision ChangesPath 1.15 +0 -8 maven/xdocs/index.xml Index: index.xml === RCS

[jira] Created: (MPXDOC-128) Internationalized Websites

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPXDOC-128 Here is an overview of the issue: - Key:

RE: Writing plugin testcases (WAS Re: [jira] Commented: (MPECLIPSE-56)Only create .classpath and javabuilder if sources are present)

- what layout should we use by default? should we use the 'single > project with one goal per testcase' or the 'multi-project with one > project per testcase'? I think that a good first place is even just letting people know that it is possible, and linking to some good examples. Unless you are a