RE: Modules location not honored when specifying several subdirs?

ot honored when specifying several subdirs? On Feb 4, 2007, at 11:52 AM, John Allen wrote: > This has been a problem for quite some time; the JIRA ticket number > escapes > me though. If I remember right its not actually all of the maven > that's > failing to use the fil

RE: Maven Site Plugin

Also worthy of note is MSITE-209 which I found a couple of weeks ago (been on holiday) J -Original Message- From: Stephane Nicoll [mailto:[EMAIL PROTECTED] Sent: 16 January 2007 19:53 To: Maven Developers List Subject: Re: Maven Site Plugin The @deprecated tag seems broken BTW. Does a

RE: [PROPOSAL] Standard Reporting

All, Re dashboards: the reporting aspect of this space is TBH the most trivial aspect of a much wider problem domain, namely that of metrics management and processing, think datum acquisition, storage, manipulation and obviously reporting/access - think OLAP; think CMMI; think corporate governance

RE: Modules location not honored when specifying several subdirs?

This has been a problem for quite some time; the JIRA ticket number escapes me though. If I remember right its not actually all of the maven that's failing to use the file system source POM, i.e. a -X dump produces a failure at a different location depending on whether the POM is actually available

RE: Publishing plugin sites

This maybe moot but this reminds me of something that bothered me a while back: The problem here is the lack of project identity (group id, artifact id, version) support in sites. A site is simply a view upon a project and yet there is no way for us to reflect which version that site was generated

RE: Maven central reporting API

repository environment. I said hope didn’t I? Glad it's an area everyone's thinking about though... :) John Allen -Original Message- From: Arnaud Bailly [mailto:[EMAIL PROTECTED] Sent: 06 September 2006 16:24 To: Maven Developers List Subject: Re: Maven central reporting API Jas

RE: Extending reporting management

Sounds like an excellent proposal. I've been thinking for some time how we might extend maven's reporting fwk to better support metrics management and reporting. Have you considered the means of making this RDF data distributable (and re-constitutable) via the maven artifact system? John -Ori

RE: General issue with clover plugin requiring creative thinking...

I have found this aspect of clover a great frustration and would welcome any attempt to separate such 'instrument and compile' tasks from the main project build activities. John -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 11 July 2006 06:20 To: Maven Developers

RE: Re: Common API for issue tracking systems

A generic activity management API would get a big +1 from me (re naming, we use JIRA for much more than bug tracking) While building an integrated ALM environment i had to cobble together some build system interfaces too - a common API for such systems would be very useful too? (LuntBuild/Quic

Re: Configure plugins through settings.xml

Tomasz Pik gmail.com> writes: > > Hello, > > It's currently not possible but generally I think it would be nice to have > possibility to configure plugins through profiles using $HOME/.m2/settings.xml Please note there are some bugs in maven that prevent all of the aspects of plugin configurat

Re: New Issue Tracking URL for the recently released plugins - is it OK?

I have to respecify my issueTracking details in module POMs that have a dedicated JIRA project. - Original Message - From: "Mike Perham" <[EMAIL PROTECTED]> To: "Maven Developers List" Sent: Thursday, May 18, 2006 11:19 PM Subject: RE: New Issue Tracking URL for the recently released

Re: aggregating report

Mike, In regards to the javadoc aggregation report, I liked the idea of generating scoped javadoc aggregtaion reports as i drilled into the project hierarchy but noticed this wasnt possible, only the top-level project of reactor env would generate the aggregation report. If this 'only perfor

[jira] Created: (MNG-2126) Snapshot plugin repositories are not searched for plugins that do not explicitly specify a snapshot version.

Project: Maven 2 Type: Bug Reporter: John Allen Priority: Minor Only release repositories are queried for version-unscoped plugins. Deploy a plugin (say x-maven-plugin, version 1-SNAPSHOT) to a snapshot repository via mvn -P performRelease deploy. clear local repository

[jira] Created: (MCHECKSTYLE-33) Patch provides ability to control whether check MOJO violations cause build failure (inline with pmd:check)

/MCHECKSTYLE-33 Project: Maven 2.x Checkstyle Plugin Type: Improvement Reporter: John Allen Attachments: CheckstyleViolationCheckMojo.diff Example: mvn -Dcheckstyle.failOnViolation=false checkstyle:check Use case: In the same way that test failures can be prevented from failing

[jira] Created: (MNG-2086) Support writing all generated output to a different filesystem base to that of the project files (i.e. all non generated files)

: http://jira.codehaus.org/browse/MNG-2086 Project: Maven 2 Type: Improvement Reporter: John Allen It is a useful and powerful feature for a build system to support using a different base directory for all generated output. This enables the project source (pom et al) to be accessed

[jira] Commented: (MRM-96) Enable the use of http proxies when mrm is restricted to browse directly over the net

[ http://jira.codehaus.org/browse/MRM-96?page=comments#action_58688 ] John Allen commented on MRM-96: --- Support NTLM HTTP proxies > Enable the use of http proxies when mrm is restricted to browse directly over > t

Re: Bug in POM validation when using dependencyManagement

I dont know whether this is a bug or not (sounds like it though) but i do know that i have had to stop using extensive property based customizations in my complex multi-project environments due to a failure of many plugins (really its an issue with the core API and not the plugins) to properly

[jira] Commented: (MNG-1931) add a reportingManagement section

[ http://jira.codehaus.org/browse/MNG-1931?page=comments#action_58533 ] John Allen commented on MNG-1931: - Any thoughts re moving this up the priority ladder? After all one of the key benefits of using maven is the reduction in duplicated configs and

[jira] Created: (MPMD-13) Provide pmd:check (patch attached)

Provide pmd:check (patch attached) -- Key: MPMD-13 URL: http://jira.codehaus.org/browse/MPMD-13 Project: Maven 2.x Pmd Plugin Type: New Feature Reporter: John Allen Attachments: PmdViolationCheckMojo.java Attached file adds a

Re: a little more on site structure

Re snapshot sites. This is exactly what i use the site:stage functionality to try and provide. In my scheme a project basically has two sites, its released site (deployed to distrMgmt::site::url) and its snapshot site. The snapshot site is generated with lots of technical reports usefull for p

Re: ${modules}

I know of one way that this can occure but only in non reactor envs (-N): if your models do not explicitly declare a URL or name then the resulting module will not be written into the final site (see http://jira.codehaus.org/browse/MSITE-72) - Original Message - From: "Brett Porter" <

[jira] Created: (MSITE-84) Refactor of site:stage and site:site required due to new site:site modules appraoch

: Improvement Reporter: John Allen site:stage was designed to provide a means of normalising all the URLs involved in a reactor built site to be local filesystem based paths allowing a complete site to be built and tested without it being deployed to the target deployment location(s) - it

[jira] Updated: (MSITE-72) new non reactor populateModules SiteMojo code assumes each POM declares its own URL

[ http://jira.codehaus.org/browse/MSITE-72?page=all ] John Allen updated MSITE-72: Attachment: SiteMojo.diff > new non reactor populateModules SiteMojo code assumes each POM declares its > o

[jira] Created: (MSITE-73) new site code fails to generate banner images in projects other than site.xml owning project

Plugin Type: Bug Reporter: John Allen root project declares site.xml containing banner:- ${project.name} images/banner-lhs.png ${project.url} This gets rendered properly in the root project site pages (e.g. index.html

[jira] Created: (MSITE-72) new non reactor populateModules SiteMojo code assumes each POM declares its own URL

: Bug Reporter: John Allen In populateModules() :- SiteMojo.java +523 File f = new File( project.getBasedir(), module + "/pom.xml" ); if ( f.exists() ) { MavenXpp3Reader reader = new Maven

[jira] Commented: (MPMD-8) PMD should generate results in formats other than html

[ http://jira.codehaus.org/browse/MPMD-8?page=comments#action_55263 ] John Allen commented on MPMD-8: --- Mike, I know it's closed, that's why I commented it, that and the fact that I didn't want my work to go to waste. But as it's now

[jira] Commented: (MPMD-3) Add support for multiple RuleSets

[ http://jira.codehaus.org/browse/MPMD-3?page=comments#action_55260 ] John Allen commented on MPMD-3: --- Mike, thanks for your work on this, just a shame ive been working on it too without realising these MPMD ones were active. I would like to make one

[jira] Commented: (MPMD-4) PMD should use "sensible" default rulesets

[ http://jira.codehaus.org/browse/MPMD-4?page=comments#action_55258 ] John Allen commented on MPMD-4: --- Over the weekend i took this code and MPMD-8 patches and went through the pmd:pmd and pmd:execute Mojos refactoring and aligning them with the other report

[jira] Commented: (MPMD-8) PMD should generate results in formats other than html

[ http://jira.codehaus.org/browse/MPMD-8?page=comments#action_55257 ] John Allen commented on MPMD-8: --- Over the weekend i took this code and MPMD-4 patches and went through the pmd:pmd and pmd:execute Mojos refactoring and aligning them with the other report

[jira] Commented: (MNG-1929) Plugin Goal report should indicate which fields are read only. (Patch Attached)

[ http://jira.codehaus.org/browse/MNG-1929?page=comments#action_55193 ] John Allen commented on MNG-1929: - +1 for not showing, readonly == private impl. > Plugin Goal report should indicate which fields are read only. (Patch > At

[jira] Commented: (MNG-1943) MavenProject::getParent() returns a MavenProject that is NOT interpolated

[ http://jira.codehaus.org/browse/MNG-1943?page=comments#action_55192 ] John Allen commented on MNG-1943: - Brett, re 'a rare case', obviously my familiarity with these internal APIs and there usage is greatly limited so I will defer to your exp

[jira] Created: (MSITE-71) Plugin uses NON interpolated model values (e.g URL) due to MavenProject.getParent returning non interpolated project

/browse/MSITE-71 Project: Maven 2.x Site Plugin Type: Bug Versions: 2.0 Reporter: John Allen Priority: Blocker You can not do this:- String parentUrl = project.getParent().getUrl(); (SiteMojo.java +928) As getParent returns a Mavenproject that has not been

[jira] Created: (MNG-1943) MavenProject::getParent() returns a MavenProject that is NOT interpolated

MavenProject::getParent() returns a MavenProject that is NOT interpolated - Key: MNG-1943 URL: http://jira.codehaus.org/browse/MNG-1943 Project: Maven 2 Type: Bug Reporter: John Allen

m2 logging

rts - Unable to distinguish what action has caused a message, part of a wider issue with not being able to associate what is being said, by who, and why (users pov) - No ability to extend message generation/delivery with adapters et

Site aggregation (Relocating discussion from confluence to dev)

Re discussion regarding site aggregation See: http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence for previous notes. Hi Brett, Re your last comments: 'The copy is done from the top level so it can run as an aggregator and the subprojects can be viewed as a single site and deployed a

[jira] Created: (MNG-1874) problems with site:stage

problems with site:stage Key: MNG-1874 URL: http://jira.codehaus.org/browse/MNG-1874 Project: Maven 2 Type: Bug Components: maven-site-plugin Versions: 2.0.2 Reporter: John Allen Fix For: 2.0.3 The patches contributed

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_53654 ] John Allen commented on MNG-661: Additionall problem with new staging functionality and accessing uninterpolated parent project attributes. project.getParent() returns a project that

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_53143 ] John Allen commented on MNG-661: re the patch, theres a bug in the SiteStageMojo::getStructure() method under windows. Windows distribution paths can start with drive prefixes and thus

[jira] Created: (MNG-1753) support improved property based profile activation

support improved property based profile activation -- Key: MNG-1753 URL: http://jira.codehaus.org/browse/MNG-1753 Project: Maven 2 Type: New Feature Components: POM Reporter: John Allen support better profile

[jira] Commented: (MNG-1525) Allow environment variables to be referenced in pom.xml, settings.xml, etc.

[ http://jira.codehaus.org/browse/MNG-1525?page=comments#action_52783 ] John Allen commented on MNG-1525: - I guess im going to have to wait for commons-exec as the only way i know of doing this robustly is via JNI (the codeset used by cmd.exe can be any

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_52782 ] John Allen commented on MNG-661: Thanks Vincent, works a treat! I'm using the staged site not only reviewing but also for internal pre-release publications (i.e. CI build generat

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_52746 ] John Allen commented on MNG-661: Vincent, the patch seems to be missing the new SiteStage mojo. > In parent site, automatically create link to modules sites and vice-ve

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_52647 ] John Allen commented on MNG-661: Hi Vincent, Yeah i think this is a more approrpiate approach, especially as its only intended for testing. So the key to the the simulate mode is that

[jira] Commented: (MNG-1643) Provide installer support like NSIS or InnoSetup

[ http://jira.codehaus.org/browse/MNG-1643?page=comments#action_52004 ] John Allen commented on MNG-1643: - brett, although i agree with you in terms of better componentisation of the design i cant think of a use case where anyone will want to make more than

[jira] Commented: (MNG-1531) add a report mojo to create a an effective pom and effective settings report (to be used in site generation)

[ http://jira.codehaus.org/browse/MNG-1531?page=comments#action_52003 ] John Allen commented on MNG-1531: - indeed regarding external publication of sensitive data but as many organisations use the maven generated project site to act as the a project&#

[jira] Commented: (MNG-1667) M2_HOME is not used in the way described in README.txt and as such bootstrap build fails

[ http://jira.codehaus.org/browse/MNG-1667?page=comments#action_51778 ] John Allen commented on MNG-1667: - >From build output:- [INFO] [INFO] BUILD SUCCESSFUL [I

[jira] Created: (MNG-1667) M2_HOME is not used in the way described in README.txt and as such bootstrap build fails

Components: bootstrap Environment: Win32 (XP SP2) Reporter: John Allen >From README.txt Set the environment variable M2_HOME pointing to the dir where you want Maven2 installed. NOTE: presently, the directory {M2_HOME}/bin must be in your path: set PATH=%PATH%;%M2_HOME%\bin or exp

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_51763 ] John Allen commented on MNG-661: Vincent, youre right regarding the limitations of using the projects 'published' URL location for building backward and fwd refs, namely that

Re: m2 developers rfc: The assembly plugin ans thirdparty installation builders

le-assembly-plugin > with its own lifecyle (package type). The plugin would issue a Commandline > to exec mvn assembly:assembly. > The lifecyle then take care of setting up the output of the assembly so that > install and deploy can do the rest. > However this implementation is

[jira] Commented: (MNG-1643) Provide installer support like NSIS or InnoSetup

[ http://jira.codehaus.org/browse/MNG-1643?page=comments#action_51683 ] John Allen commented on MNG-1643: - Works a treat. Theres a minor change required to the download report mojo to map the custom installer formats to be refered to as exes when building

[jira] Commented: (MNG-1643) Provide installer support like NSIS or InnoSetup

[ http://jira.codehaus.org/browse/MNG-1643?page=comments#action_51635 ] John Allen commented on MNG-1643: - Thanks for the JIRA, will review shortly (day job getting in the way...) > Provide installer support like NSIS or InnoSe

New plugin submitted: http://jira.codehaus.org/browse/MOJO-126

New plugin submitted: http://jira.codehaus.org/browse/MOJO-126

m2 developers rfc: The assembly plugin ans thirdparty installation builders (REPOST)

Hi, This is a reposting looking for comments from m2 developers. I am in the process of writing a NullSoft Installer plugin and wish to discuss its design and usage in respect to the assembler plugin. The assembly plugin has been designed to operate in a stand-alone fashion, firing off the pro

The assembly plugin (and its uses in other installer/distribution builders)

Request for comments: How should I go about designing a NullSoft Installer plugin so that it works well with the assembly paradigm? The assembly plugin seems to have been designed to operate in a stand-alone fashion, firing off the project's package build, rather than cooperate within the ex

[jira] Created: (MNG-1531) add a report mojo to create a an effective pom and effective settings report (to be used in site generation)

Project: Maven 2 Type: New Feature Reporter: John Allen add a report mojo so that we can include the effective pom and effective settings in a project's site reports. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one o

[jira] Updated: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=all ] John Allen updated MNG-661: --- Attachment: SiteMojoPatch.txt Sigh. i got the whole distributionManagement::site::URL thing about face, taking the distro site details to reflect the projects site'

[jira] Updated: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=all ] John Allen updated MNG-661: --- Attachment: SiteMojoPatch.txt My bad, missed bug for leaf nodes that resulted in empty modules menu. New patch has one line difference to previous patch, namely line 791 (in

[jira] Updated: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=all ] John Allen updated MNG-661: --- Attachment: SiteMojoPatch.txt Patch reinstates modules support through use of reactor projects and the parsing of their distributionManagement site information. > In par

[jira] Created: (MNG-1398) site report generates an 'empty' target/site/apidocs/index.html

Versions: 2.0 (RC) Reporter: John Allen javadoc site report generates an 'empty' target/site/apidocs/index.html ... © 2005 Acme Org -- This mess

[jira] Created: (MNG-1009) Is it possible for all plugins to suport a common goal that causes the plugin to describe itself, its goals and its properties?

: http://jira.codehaus.org/browse/MNG-1009 Project: Maven 2 Type: Improvement Components: maven-plugin-api Reporter: John Allen Would it be sensical (not to mention possible) to have all plugins suport a common goal that causes the plugin to describe itself, its goals and its

[jira] Created: (MNG-965) Provide new javadoc:aggregate goal to perform javadoc operation on project and subprojects.

: Improvement Components: maven-javadoc-plugin Reporter: John Allen Priority: Minor Provide new javadoc:aggregate goal to perform javadoc operation on a project and its subprojects, idea being that aggregate pulls together the classpath and sourcepath for all the project and subprojects

[jira] Commented: (MNG-942) Ability to source system properties in settings.xml

[ http://jira.codehaus.org/browse/MNG-942?page=comments#action_46854 ] John Allen commented on MNG-942: > " (I'm assuming that by 'source Java System properties' you mean setting > them, like System.setProperty or -Dprop=val)

[jira] Created: (MNG-942) Ability to source system properties in settings.xml

java version "1.5.0_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05) Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode) Reporter: John Allen Priority: Trivial Would be nice to be able to source Java System properties in the global and user setting

[jira] Created: (MNG-941) Deletion of ~/.m2 directory prevents (re)creation of plugin-registry.xml file with java.io.FileNotFoundException

/MNG-941 Project: Maven 2 Type: Improvement Environment: WIN XP Pro, SP2 java version "1.5.0_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05) Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode) Reporter: John Allen Priority: Minor Deletio