Hello,

I would like to submit a JIRA improvement request for the maven 2 dashboard
plugin, but I could not find a JIRA project for this maven 2 plugin. All I
could find on http://jira.codehaus.org/ is a project for Maven 1.x Dashboard
plugin. Could you, pls, tell me which JIRA project to use?

Thanks,

Venelin

2008/1/29, dvicente <[EMAIL PROTECTED]>:
>
>
> HI,
>
> and i've made a response :
>
> no, at this moment, the historic results are stored by version.
>
> the reason is , in many companies, you must developp with a trunk version
> with current developpment and a branch version for correction and each
> version must have its own historic.
>
> it will be possible to disregard the version with a configuration
> parameter
> in the future but you must create a JIRA issue for that.
>
> Best regards
>
> David Vicente
>
> torsten.reinhard wrote:
> >
> > Hi,
> >
> > I´ve asked the same question a few days ago, see below.
> > Please let me know if there´s any simple workaround (not copying and
> > manipulating the database each day:-))
> >
> > Will you create a JIRA for that ?
> >
> > CU, torsten
> >
> >
> >
> >
> > "Venelin Mitov" <[EMAIL PROTECTED]>
> > 28.01.2008 18:56
> > Bitte antworten an
> > [email protected]
> >
> >
> > An
> > [email protected]
> > Kopie
> >
> > Thema
> > [mojo-user] Empty historical charts in the maven dashboard plugin after
> > changing the project version
> >
> >
> >
> >
> >
> >
> > Hello,
> >
> > Is it possible to avoid "loosing the history" in the
> > maven-dashboard-report after changing the project version? It would be
> > perfect to display in the same chart how the quality of the project code
> > evolves between different project releases.
> >
> > Kind regards,
> >
> > Venelin MITOV
> >
> >
> ________________________________________________________________________________________________________________________
> >
> >
> > HI,
> >
> > no, at this moment, the historic results are stored by version.
> >
> > the reason is , in many companies, you must developp with a trunk
> version
> > with current developpment and a branch version for correction and each
> > version must have its own historic.
> >
> > it will be possible to to disregard the version with a configuration
> > parameter in the future but you must create a JIRA issue for that.
> >
> > Best regards
> >
> > David Vicente
> >
> > 2008/1/22, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> >
> > Hi,
> >
> > I´ve had a pom.xml like
> >
> > ...
> > <artifactId>myartifact</artifactId>
> > <groupId>mycompany.mygroup </groupId>
> > <version>2.5.5</version>
> > ...
> >
> > The dashboard maven plugin worked fine, i enjoyed the historic page very
> > much.
> >
> > Now, in our developement process, we often change between SNAPSHOT and
> > Releaseversions.
> > Each change of the <version> tag in pom.xml results in a new generated
> > MAVENPROJECT_ID value in the database of the dashboard plugin.
> >
> > The MAVENPROJECT table looks like
> >
> > MAVENPROJECT_ID         GROUPID                ARTIFACTID        VERSION
> >   ...
> > ===============================================================
> >         16                com.gide.crypto        gide-crypto-util 2.5.5
> >         294913                com.gide.crypto        gide-crypto-util
> > 3.0.0-SNAPSHOT
> >         ...                com.gide.crypto        gide-crypto-util
> > 3.0.1-SNAPSHOT
> >
> > The generated historic page of one module now only contains the recently
> > stored information - the information from the last "stable version
> phase".
> >
> >
> > => Is there a way to get a whole historic view (all versions) of one
> > module ?
> >
> >
> > Thanx, Torsten
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Empty-historical-charts-in-the-maven-dashboard-plugin-after-changing-the-project-version-tp15141097p15153685.html
> Sent from the mojo - user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>


-- 
Venelin MITOV

Reply via email to