Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Rémy Sanlaville]

Great, thank you Hervé!

Regards,
Rémy

On Fri, Apr 16, 2021 at 7:25 AM Hervé BOUTEMY  wrote:

> thank you Remi
>
> PR merged and current release HTML tweaked [1] to benefit from the
> documentation  just now
>
> Regards,
>
> Hervé
>
>
> https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/examples/rollback-release.html
>
> Le jeudi 15 avril 2021, 22:38:05 CEST Rémy Sanlaville a écrit :
> > Hi Hervé,
> >
> > PR created (cf. https://github.com/apache/maven-release/pulls)
> >
> > Regards,
> > Rémy
> >
> > On Wed, Apr 14, 2021 at 1:28 PM Hervé BOUTEMY 
> wrote:
> > > please create the PR to have it merged
> > >
> > > and given it's documentation, we can eventually modify HTML by hand to
> > > have
> > > this nice little improvement in the current release documentation...
> > >
> > > Le mercredi 14 avril 2021, 09:36:52 CEST Rémy Sanlaville a écrit :
> > > > Hi Robert,
> > > >
> > > > I understand. I wasn't aware about
> > > > https://github.com/apache/maven-release/pulls
> > > >
> > > > I was just aware to edit the page as you asked me
> > > >
> > > > > There's an edit-button on the page (upper left in nav bar) that
> links
> > >
> > > to
> > >
> > >
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven
> > >
> > > > > -release-plugin/src/site/apt/examples/rollback-release.apt Would be
> > >
> > > great
> > >
> > > > > if you could help updating this page.
> > > > >
> > > > > Cf.
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbir
> > > d-> 3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> > >
> > > > Rémy
> > > >
> > > > On Tue, Apr 13, 2021 at 5:49 PM Robert Scholte  >
> > >
> > > wrote:
> > > > > Hi Rémy
> > > > >
> > > > > I don't see it as PR under
> > >
> > > https://github.com/apache/maven-release/pulls
> > >
> > > > > I did a quick scan over this list and the open Jira issues and
> decided
> > >
> > > not
> > >
> > > > > to add more to this milestone release.
> > > > >
> > > > > Robert
> > > > > On 13-4-2021 09:09:21, Rémy Sanlaville 
> > >
> > > wrote:
> > > > > Hi Robert,
> > > > >
> > > > > What about
> > >
> > >
> https://github.com/apache/maven-release/compare/master...sanlaville:patch-
> > > >
> > >
> > > > 1
> > > >
> > > > > ?
> > > > >
> > > > > Cf.
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1
> > >
> > > > > TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com
> %3E
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbir
> > >
> > > > > d-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> > > > >
> > > > > Rémy
> > > > >
> > > > > On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:
> > > > > > Hi,
> > >
> > > > > > We solved 5 issues:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824;
> > >
> > > > > version=12348079=Text>
> > > > >
> > > > > > There are still a couple of issues left in JIRA:
> > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317824%20AND%
> > >
> > >
> 20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20
> > >
> > > > > DESC>
> > > > >
> > > > > > Staging repo:
> > > > > > https://repository.apache.org/content/repositories/maven-1639
> > >
> > >
> https://repository.apache.org/content/repositories/maven-1639/org/apache/m
> > >
> > >
> aven/release/maven-release/3.0.0-M4/maven-release-3.0.0-M4-source-release.
> > >
> > > > > zip>
> > > > >
> > > > > > Source release checksum(s):
> > >
> > > > > > maven-release-3.0.0-M4-source-release.zip sha512:
> > >
> 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702
> > >
> > > > > 205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895>
> > > > >
> > > > > > Staging site:
> > > > > >
> https://maven.apache.org/maven-release-archives\maven-release-LATEST
> > >
> > > > > > Guide to testing staged releases:
> > >
> https://maven.apache.org/guides/development/guide-testing-releases.html
> > >
> > > > > > Vote open for at least 72 hours.
> > > > > >
> > > > > > [ ] +1
> > > > > > [ ] +0
> > > > > > [ ] -1
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Rémy Sanlaville]

Hi Hervé,

PR created (cf. https://github.com/apache/maven-release/pulls)

Regards,
Rémy

On Wed, Apr 14, 2021 at 1:28 PM Hervé BOUTEMY  wrote:

> please create the PR to have it merged
>
> and given it's documentation, we can eventually modify HTML by hand to
> have
> this nice little improvement in the current release documentation...
>
> Le mercredi 14 avril 2021, 09:36:52 CEST Rémy Sanlaville a écrit :
> > Hi Robert,
> >
> > I understand. I wasn't aware about
> > https://github.com/apache/maven-release/pulls
> >
> > I was just aware to edit the page as you asked me
> >
> > > There's an edit-button on the page (upper left in nav bar) that links
> to
> > >
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven
> > > -release-plugin/src/site/apt/examples/rollback-release.apt Would be
> great
> > > if you could help updating this page.
> > >
> > > Cf.
> >
> >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird->
> 3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> >
> > Rémy
> >
> > On Tue, Apr 13, 2021 at 5:49 PM Robert Scholte 
> wrote:
> > > Hi Rémy
> > >
> > > I don't see it as PR under
> https://github.com/apache/maven-release/pulls
> > > I did a quick scan over this list and the open Jira issues and decided
> not
> > > to add more to this milestone release.
> > >
> > > Robert
> > > On 13-4-2021 09:09:21, Rémy Sanlaville 
> wrote:
> > > Hi Robert,
> > >
> > > What about
> > >
> https://github.com/apache/maven-release/compare/master...sanlaville:patch->
> > 1
> > > ?
> > >
> > > Cf.
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1
> > > TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbir
> > > d-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> > >
> > > Rémy
> > >
> > > On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:
> > > > Hi,
> > >
> > > > We solved 5 issues:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824;
> > > version=12348079=Text>
> > > > There are still a couple of issues left in JIRA:
> > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317824%20AND%
> > >
> 20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20
> > > DESC>
> > > > Staging repo:
> > > > https://repository.apache.org/content/repositories/maven-1639
> > >
> > >
> https://repository.apache.org/content/repositories/maven-1639/org/apache/m
> > >
> aven/release/maven-release/3.0.0-M4/maven-release-3.0.0-M4-source-release.
> > > zip>
> > > > Source release checksum(s):
> > >
> > > > maven-release-3.0.0-M4-source-release.zip sha512:
> > >
> 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702
> > > 205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895>
> > > > Staging site:
> > > > https://maven.apache.org/maven-release-archives\maven-release-LATEST
> > > >
> > > > Guide to testing staged releases:
> > > >
> https://maven.apache.org/guides/development/guide-testing-releases.html
> > > >
> > > > Vote open for at least 72 hours.
> > > >
> > > > [ ] +1
> > > > [ ] +0
> > > > [ ] -1
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Rémy Sanlaville]

Hi Robert,

I understand. I wasn't aware about
https://github.com/apache/maven-release/pulls

I was just aware to edit the page as you asked me

> There's an edit-button on the page (upper left in nav bar) that links to 
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven-release-plugin/src/site/apt/examples/rollback-release.apt
> Would be great if you could help updating this page.
>
> Cf.
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E

Rémy

On Tue, Apr 13, 2021 at 5:49 PM Robert Scholte  wrote:

> Hi Rémy
>
> I don't see it as PR under https://github.com/apache/maven-release/pulls
> I did a quick scan over this list and the open Jira issues and decided not
> to add more to this milestone release.
>
> Robert
> On 13-4-2021 09:09:21, Rémy Sanlaville  wrote:
> Hi Robert,
>
> What about
> https://github.com/apache/maven-release/compare/master...sanlaville:patch-1
> ?
>
> Cf.
>
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
>
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
>
> Rémy
>
> On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:
>
> > Hi,
> >
> > We solved 5 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317824%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1639
> >
> >
> https://repository.apache.org/content/repositories/maven-1639/org/apache/maven/release/maven-release/3.0.0-M4/maven-release-3.0.0-M4-source-release.zip
> >
> > Source release checksum(s):
> >
> > maven-release-3.0.0-M4-source-release.zip sha512:
> 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895
> >
> > Staging site:
> > https://maven.apache.org/maven-release-archives\maven-release-LATEST
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Rémy Sanlaville]

Hi Robert,

What about
https://github.com/apache/maven-release/compare/master...sanlaville:patch-1
?

Cf.
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E

Rémy

On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte  wrote:

> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317824%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1639
>
> https://repository.apache.org/content/repositories/maven-1639/org/apache/maven/release/maven-release/3.0.0-M4/maven-release-3.0.0-M4-source-release.zip
>
> Source release checksum(s):
>
> maven-release-3.0.0-M4-source-release.zip sha512: 
> 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895
>
> Staging site:
> https://maven.apache.org/maven-release-archives\maven-release-LATEST
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

Re: [ANN] Apache Maven Release Plugin 3.0.0-M1 Released

[Rémy Sanlaville]

Hello Robert,

I wasn't aware of this possibility.
Done on branch master :
https://github.com/apache/maven-release/compare/master...sanlaville:patch-1

Regards,
Rémy

On Wed, Jun 17, 2020 at 6:08 PM Robert Scholte  wrote:

> There's an edit-button on the page (upper left in nav bar) that links to
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven-release-plugin/src/site/apt/examples/rollback-release.apt
> Would be great if you could help updating this page.
>
> thanks,
> Robert
>
>

Re: [ANN] Apache Maven Release Plugin 3.0.0-M1 Released

[Rémy Sanlaville]

Hello,

FYI, it seems that the page rollback-release.html

was not updated with the release 3.0.0-M1:
  - RELEASE-229  was fixed by
3.0.0-M1 release
  - the JIRA link is wrong : http://jira.codehaus.org/browse/MRELEASE-229
should be replace by https://issues.apache.org/jira/browse/MRELEASE-229

Thanks for having fixing MRELEASE-229


Rémy

On Mon, Dec 16, 2019 at 9:02 AM Hervé Boutemy  wrote:

> The Apache Maven team is pleased to announce the release of the Apache
> Maven Release Plugin, version 3.0.0-M1.
>
> This plugin is used to release a project with Maven, saving a lot of
> repetitive, manual work. Releasing a project is made in two steps: prepare
> and perform.
>
> https://maven.apache.org/plugins/maven-release-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> 
>   org.apache.maven.plugins
>   maven-release-plugin
>   3.0.0-M1
> 
>
> You can download the appropriate sources etc. from the download page:
>
> https://maven.apache.org/plugins/maven-release-plugin/download.cgi
>
>
> Release Notes - Maven Release Plugin - Version 3.0.0-M1
>
> ** Bug
> * [MRELEASE-229] - release:rollback is missing remove tag
> implementation
> * [MRELEASE-601] - The Maven 2 release plugin modifies CDATA elements
> in pom.xml files.
> * [MRELEASE-694] - -SNAPSHOT is unexpectedly appended to version in
> branched pom.xml
> * [MRELEASE-908] - Git HTTP authentication failing if there are spaces
> in the password
> * [MRELEASE-928] - exposing the password for SCM URL if build failed
> to commit files to SCM
> * [MRELEASE-947] - Wiki page URL for maven-release-plugin is wrong -
> post Codehaus termination
> * [MRELEASE-964] - Error injecting:
> org.apache.maven.shared.release.phase.RewritePomsForReleasePhase
> * [MRELEASE-966] - release plugin does not respect "mvn -f"
> * [MRELEASE-968] - Maven release plugin missing plexus-cipher
> dependency
> * [MRELEASE-975] - NPE when using an unknown project versionpolicy id
> * [MRELEASE-997] - Unable to release:perform on windows if a file name
> contains spaces on windows
> * [MRELEASE-1009] - Compilation failure when using Java 10
> * [MRELEASE-1034] - Remove SCM tag blocks rollback in some situations
>
> ** New Feature
> * [MRELEASE-956] - Release Strategy Interface
> * [MRELEASE-980] - Provide the ability to control commit messages
> * [MRELEASE-985] - Override SNAPSHOT dependencies from command line
> * [MRELEASE-998] - Add ability to create custom phases
> * [MRELEASE-1029] - update project.build.outputTimestamp property on
> prepare
> * [MRELEASE-1031] - display release phases to give insight on what's
> going on during release
>
> ** Improvement
> * [MRELEASE-703] - [PATCH] Migration from obsolete plexus-maven-plugin
> to plexus-containers-component-metadata
> * [MRELEASE-873] - Remove possibly confusing non-standard goals from
> example
> * [MRELEASE-896] - Disable by default and deprecate useReleaseProfile
> parameter
> * [MRELEASE-909] - Add workItem/task support for scm deliver
> * [MRELEASE-958] - Using three digit version number (semver)
> * [MRELEASE-976] - release:branch should also support project version
> policies
> * [MRELEASE-977] - release:branch should prompt for branch name if
> none is given
> * [MRELEASE-979] - Support NamingPolicies to manage Branch and Tag
> names
> * [MRELEASE-992] - Deprecated maven flag --no-plugin-updates shows
> warnings in the console output
> * [MRELEASE-993] - Use shallow checkout per default (git scm)
> * [MRELEASE-994] - Drop Maven2 support
> * [MRELEASE-1005] - Extract ResourceGenerator from ReleasePhase
> * [MRELEASE-1007] - Rework usage workingDirectory and commonBasedir
> * [MRELEASE-1023] - Minor code cleanups
> * [MRELEASE-1032] - add https://m.a.o/xsd/maven-4.0.0.xsd schema
> instead of http://m.a.o/maven-v4_0_0.xsd
>
> ** Task
> * [MRELEASE-356] - Deprecate the automated release profile
> * [MRELEASE-990] - switch to Git
> * [MRELEASE-1027] - New Release
> * [MRELEASE-1033] - Site: Dead link to wiki
>
> ** Dependency upgrade
> * [MRELEASE-952] - Replace JDom as XML transformer
> * [MRELEASE-1010] - Upgrade maven-plugins parent to version 32
> * [MRELEASE-1024] - Upgrade to SCM 1.11.2
>
> Enjoy,
>
> -The Apache Maven team
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

IoC applied to build tools?

[Rémy Sanlaville]

Consider the following project:
P1
  m1
  m2
 m2.1
 m2.2
  m3
 m3.1
 m3.2
 m3.3
--- pom.xml

For testing, mocking, prototyping... we often want to be able to replace a
set of modules/artifacts by new modules/artifacts: for instance m1, m2.2 and
m3.3 by m1-mock, m2.2-test and m3.3-test.
It's not easy to do it: either you have to generate different artifacts with
the same name (with different behavior...) or to modify your
modules/dependencies + use of profiles which complicates the build. It's not
really what we want to do.
How do you cope with this?

A solution could be to applied IoC to maven.
Somethings like this

(P1) pom.xml

dependencyManagement
  dependency ref=ref-m1/

  dependency
groupId.../groupIdp
artifactIdm2.1/artifactId
  /dependency

  dependency ref=ref-m2.2/

   ...
/dependencyManagement


modules
  module ref=ref-m1/
  modulem2/module
  modulem3/module
/modules

with different configurations
c1:
  bean id=ref-m1 module=m1
 property name=artifactId value=m1 /
 ...
  /bean

  bean id=ref-m2.2 module=m2.2
 property name=artifactId value=m2.2 /
 ...
  /bean

  bean id=ref-m3.3module=m3.3
  property name=artifactId value=m3.3 /
 ...
  /bean

and c2:
!--
  bean id=ref-m1 module=m1-mock
 property name=artifactId value=m1-mock /
 ...
  /bean

!-- module and artifactId value could be different for instance we just
want to replace
  the m2.2 artifact by its corresponding test artifact m2.2-test but not
the name of the module --
  bean id=ref-m2.2 module=m2.2
 property name=artifactId value=m2.2 /
 property name=classifier value=test /
 ...
  /bean

  bean id=ref-m3.3module=m3.3
  property name=artifactId value=m3.3 /
 property name=classifier value=test /
 ...
  /bean

What do you think about it?

Rémy

Re: Getting Maven Site Plugin 2.1 out the door...

[Rémy Sanlaville]

It's a great new. Thanks Dennis for the initiative.

 2. Which issues do we include?

 Here's a list of the issues currently scheduled for the above releases:

 http://jira.codehaus.org/browse/MSHARED-102
 http://jira.codehaus.org/browse/DOXIA-354
 http://jira.codehaus.org/browse/DOXIA-355
 http://jira.codehaus.org/browse/DOXIASITETOOLS-32
 http://jira.codehaus.org/browse/MSITE-227
 http://jira.codehaus.org/browse/MSITE-244
 http://jira.codehaus.org/browse/MSITE-273
 http://jira.codehaus.org/browse/MSITE-358
 http://jira.codehaus.org/browse/MSITE-419

 I propose that we fix only DOXIASITETOOLS-32 (Deployed
 decoration-1.0.1.xsd) and MSITE-419 (Update to Doxia 1.1.2). We push the
 rest to later versions. What do other think?


That's really nice. We are waiting for MSITE-419 (see
http://jira.codehaus.org/browse/MSCMCHGLOG-15).

Rémy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Adding a Looking for Code Quality Managers section into the Maven web site ?

[Rémy Sanlaville]

+1 (non-binding)

In that connection, it would be nice to don't forget
MPIR-149http://jira.codehaus.org/browse/MPIR-149

Rémy

Re: [VOTE] Maven 2.2.0 (Fourth Attempt)

[Rémy Sanlaville]

On Mon, Jun 29, 2009 at 4:28 AM, Paul Benedict pbened...@apache.org wrote:

 Will the release notes contain any general justification for an
 upgrade? For example, can it highlight the major improvements between
 2.1 and 2.2? or 2.0 and 2.2?


 +1

Totally agree. It starts to be very difficult for user to follow/understand
the reason of such prolific major/minor version in a short time.

Rémy

Re: Using GIT as the canonical repository for Maven 3.x

[Rémy Sanlaville]

Do you see that Google choose Mercurial rather than Git ?

Mercurial support for Project Hosting on Google Code
http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html

Analysis of Git and Mercurial
http://code.google.com/p/support/wiki/DVCSAnalysis

Rémy

Re: [vote] promote pdf plugin

[Rémy Sanlaville]

big +1 (thanks).

Just try it for a project. I have to dig a little because I have two parsing
error like:
Embedded error: Error parsing ...\src\site\fml\doc\faq.fml: Error validating
the model: Error:
  Public ID: null
  System ID: null
  Line number: 6
  Column number: 17
  Message: cvc-elt.1: Cannot find the declaration of element 'faqs'.

It works if I suppress this two pages.


Otherwise three possible improvements:
  1. Why it's a (build) plugin and not a report plugin ?
  2. Why don't you use it for the maven-pdf-plugin site ?
  3. Ignore pages with error parsing (add a WARNING log) in order to not
stop the build process

And one wish:
  1. (Seems to be difficult) Generate and attach a pdf by page in the maven
web site

Rémy

Re: Extending the maven pom.

[Rémy Sanlaville]

It's an important requirement.
Have a look for instance http://jira.codehaus.org/browse/MPIR-149

Rémy

Re: RFC : integration tests

[Rémy Sanlaville]

Hi Nicolas,

I agree that integration-test is not enough support with maven.

I thought that src/it/ and target/it was the original convention (even if it
is not really used because of the lack of integration with maven 2.0.x).

It would be really nice to have a better and standard support for
integration-tests and a document that describes how to manage
integration-tests with maven 2.

Rémy

Re: [VOTE] Release Maven Release plugin version 2.0-beta-8

[Rémy Sanlaville]

+1 (non-binding)
Thanks

Rémy

Re: compiler plugin: separate test compiler configuration

[Rémy Sanlaville]

Hi,

We are also interesting for a such feature.
I just wonder if it is not possible to use the testCompile goal for that ?

Thanks,

Rémy

Re: compiler plugin: separate test compiler configuration

[Rémy Sanlaville]

Yes Milos, it was my question.

In fact, it's nice to can specify specific configuration for both source and
test.

For instance, we want to be able to define the source and target level but
also some other configuration such as compilerArgument and so on

Rémy

Re: Maven release plugin

[Rémy Sanlaville]

Hi,

ping again...

2008/9/25 Olivier Lamy [EMAIL PROTECTED]

 Oups (it looks my name here in the previous email :-) ).

 I can but first I'd like to release invoker plugin 1.3.


Now that maven invoker plugin 1.3  is released (cf.
http://www.nabble.com/-ANN--Maven-Invoker-Plugin-1.3-Released-td19727479.html#a19727479),
is that possible to release maven release plugin ?

Thanks,

Rémy

Re: Encoding issues with images using dependency and resource plugins?

[Rémy Sanlaville]

Hi,

I don't know if it can help but in case...
Did you see this thread ?
http://www.nabble.com/damage-image-files-td15431864.html#a15432280

Rémy

Re: Wagon changes and WebDAV

[Rémy Sanlaville]

 Plain PUT does not work if the directory doesn't exist yet. (That's part
 of the HTTP spec).
 You need something to create the directory (or Collection in WebDAV
 Terms), this is the MKCOL method.

 While it is true that FTP is also a provider, it should be painfully
 obvious that all existing repository manager implementations support
 WebDAV.  And it's a favorite deployment technique in corporate
 environments for the security aspects alone.

 Sure you could accomplish the same thing with SSH, but how many people
 do you find asking for deploy:deploy-file with ssh in the users list?
 In many corporations I've been involved in SSH is fine for many tasks,
 but not repository management for the rank and file or for the
 continuous integration server.  (Typically due to political and
 maintenance reasonsnot for technical ones)

 We have clear trend established with the users (in the mailing list and
 jira) that webdav is a popular choice, and the deploy:deploy-file is
 painful without it being in core, and also no option to build a custom
 client with it embedded (classloader yech, yada yada).  bringing it in
 via the command line isn't an option.  So we're left with creating a pom
 just to use deploy:deploy-file with webdav.


It's exaclty the problem we are confroted with at the moment.
It's a real pain for us and we are still looking for a solution.

It's really difficult to manage a maven 2 repository with corporate policy
access.
For instance :
inhouse
   - groupId1 (allow read/write for the team project/ read for all)
   - groupId2 (allow read/write for the team project/ read for all)
inhouse.snapshot
   - groupId1 (allow read/write for the team project/ read for all)
   - groupId2 (allow read/write for the team project/ read for all)

How to do it ?
We first try with the scp/sftp protocol but it's not working (cf.
http://www.nabble.com/-M2--Pb-Release-and-preserve-timestamps-td13626985s177.html#a13626985
).
We now try with the webdav protocol but it's not working because PUT does
not work if the directory doesn't exist yet

If you have a solution, it would be fantastic !

Rémy

Re: http://jira.codehaus.org/browse/MCHANGES-78

[Rémy Sanlaville]

Hi,

Really nice !
Hope that it will be integrated in the maven-changes-plugin and released
soon.

Rémy

Re: myfaces-master-pom and pmd reports

[Rémy Sanlaville]

Hi,

A better solution would be to improve the pmd plugin in order to be smart
enough not to generate any output if they have no input files. Isn't it ?

Regards,

Rémy

2008/1/12, simon [EMAIL PROTECTED]:

 Hi All,

 Currently the master pom defines the pmd plugin in the reporting
 section. Unfortunately it appears that while most report plugins are
 smart enough not to generate any output if they have no input files, pmd
 does not do this. As a result, every project module (which is just
 generating a site) gets pointless CMD and PMD reports (which causes the
 creation of a whole project reports menu to hold them).

 Solution (1) is to just take this definition out of the master pom, and
 have modules that want pmd/cmd reports define the plugin.

 Solution (2) is for each project module to disable these reports by
 defining an empty reportSet.

 Solution (3) is to live with these pointless project reports menus
 containing pointless cmd/pmd report pages.

 I'm in favour of (1) myself, although (2) is also possible (I have just
 done this for core12 module a few minutes ago).

 What would you prefer?

 Regards,
 Simon


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

Re: [maven-dependency-plugin] Analyze HTML Report

[Rémy Sanlaville]

Hi Brian,

It's controlled by a flag you can turn on and off.


Yes, it's true. I haven't pay enough attention.
cf. ignoreNonCompile :
http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html

The reason it's off by default is because you may have something required to
 run the tests, but would show up as an unused dependency because it's not
 compiled in to the tests directly. An example could be hyper sql used to
 simulate a database. It's referenced via a jdbc connect string, but isn't
 compiled in, even in the tests.


It's a common problem with dynamic instantiation.
I understand why you skip runtime and test (test-runtime scope does not
exist) scope.
But what about the provide scope ? I think, by default, it should not be
skipped as for the compile scope.


(The unused dependencies are determined with bytecode analysis)


It would be nice if the maven-dependy-plugin:analyse could also indicate
which classes used undeclared dependencies.
For the moment, it indicates which dependencies are missing (that is nice).
But it's also interesting to know which classes used these missing
dependencies. Do you think that it's possible to add this feature easily ?

Rémy

Re: [maven-dependency-plugin] Analyze HTML Report

[Rémy Sanlaville]

Very nice.

Brian, I wonder why the analyze goal of the maven-dependency-plugin just
take the compile dependencies for the Unused declared dependencies [1] ? Why
don't it take the test dependencies even though it also analyzes the test
classes ?

[1]
http://maven.apache.org/plugins/maven-dependency-plugin/xref/org/apache/maven/plugin/dependency/AnalyzeMojo.html#201

Thanks,

Rémy

Re: [Proposal] Skip feature

[Rémy Sanlaville]

Vote for http://jira.codehaus.org/browse/MNG-3102



Done ! Thanks.
It would be nice to increase the priority at major...

Rémy

[Proposal] Skip feature

[Rémy Sanlaville]

As we can see, the skip feature is very useful and the demand is high.
Some plugins like DbUnit, Hibernate3, SQL, PMD have implemented this
feature.
For some others, a jira is created : checkstyle (
http://jira.codehaus.org/browse/MCHECKSTYLE-43),
antrun (http://jira.codehaus.org/browse/MANTRUN-65)...

So I wonder, if it will not be better to can manage this feature at the
maven or plexus level
instead of the plugins level.

It could also be interesting to define some categories like :
- maven.test.skip
- maven.analysis.skip (cf.
http://jira.codehaus.org/browse/MCHECKSTYLE-43)
- ...

Rémy

Re: 2.0.6: Install fails but compile works. 2.0.5: Install works, compile works:

[Rémy Sanlaville]

Use the user mailing list instead.

Seems to be http://jira.codehaus.org/browse/MNG-2921

HTH,

Rémy

2007/4/24, jallen [EMAIL PROTECTED]:



Weird,

With 2.0.6 my multi-module simple J2EE app fails in the compile phase of
my
servlets child module during an install run of the reactor. However, it
all
builds if the reactor build is simply 'compile'. Also, If I cd into the
servlets module after the failed install build and just run install
locally
there, it works.

If I drop to 2.0.5 or 2.0.4 it all builds fine.

Looking at the attached logs you'll see that for the 'mvn –X install'
blows
up in the servlets module due to the missing EJB dependency.



GOOD (mvn-2.0.6 –X compile):


[INFO] [compiler:compile]
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories:

[D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\src\main\java]
[DEBUG] Classpath:

[D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\target\classes


D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-engine\target\classes


D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-ejb\target\classes
D:\APT\local-repository\javax\j2ee\j2ee\1.4\j2ee-1.4.jar]
[DEBUG] Output directory:

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\target\classes
[DEBUG] Classpath:
[DEBUG]

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\target\classes
[DEBUG]

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-engine\target\classes
[DEBUG]

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-ejb\target\classes
[DEBUG]  D:\APT\local-repository\javax\j2ee\j2ee\1.4\j2ee-1.4.jar
[DEBUG] Source roots:
[DEBUG]

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\src\main\java
Compiling 8 source files to

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\target\classes
[INFO]


[INFO] Building Calculator Webapp
[INFO]task-segment: [compile]



BAD (mvn-2.0.6 –X install):

[INFO] [compiler:compile]
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories:

[D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\src\main\java]
[DEBUG] Classpath:

[D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\target\classes

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-engine\target\classes
D:\APT\local-repository\javax\j2ee\j2ee\1.4\j2ee-1.4.jar]
[DEBUG] Output directory:

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\target\classes
[DEBUG] Classpath:
[DEBUG]

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\target\classes
[DEBUG]

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-engine\target\classes
http://www.nabble.com/file/8071/logs.zip logs.zip
[DEBUG]  D:\APT\local-repository\javax\j2ee\j2ee\1.4\j2ee-1.4.jar
[DEBUG] Source roots:
[DEBUG]

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\src\main\java
Compiling 8 source files to

D:\APT\projects\apt-examples\calculator\calculator-root\..\calculator-servlets\target\classes
[INFO]

[ERROR] BUILD FAILURE
[INFO]


How, err, can this be?



--
View this message in context:
http://www.nabble.com/2.0.6%3A-Install-fails-but-compile-works.-2.0.5%3A-Install-works%2C-compile-works%3A-tf3639635s177.html#a10164169
Sent from the Maven Developers mailing list archive at Nabble.com.

Re: [Proposal] New profile activation

[Rémy Sanlaville]

Hi Wayne

Yes, you have right. It certainly the best solution and it will be simpler.
I also think that it better to use profile just for some cases.
I was looking for this feature. As it doesn't exist yet, I used profiles
instead.

Rémy

2007/2/17, Wayne Fay [EMAIL PROTECTED]:


Would it perhaps be sufficient to add a skip configuration to all
plugins, such that you could declare the plugin the parent, and then
add a skiptrue in the plugin definition in the children which would
cause that plugin to be skipped for that specific child/module?

Just trying to think of some ways to implement this feature request...

Wayne

Re: [Proposal] New profile activation

[Rémy Sanlaville]

Hi Kennedy,


Just trying to think of some ways to implement this feature request...

I think this is the only feasible option right now.



Yes, and it's better to use the Wayne's proposal.

'site' is not a phase, it's a lifecycle. It may be possible

to add a profile activator based on lifecycle. It's not
possible (at least right now) to activate a profile
for a specific phase.
POM files are fully resolved (interpolated, merged, profiles
applied) before any phase is executed. What would happen
if you added a profile for phase test that added some modules?
If you mvn test, first compile is called on all projects
but the modules, then test is executed but there won't be
any tests to execute.



Thanks for the information. It's a little bit clearer now.

Rémy

[Proposal] New profile activation

[Rémy Sanlaville]

I would like to propose a new profile activation.

As described in
http://www.nabble.com/Execute-only-in-the-parent-POM-and-some-sub-modules---tf3201453s177.html#a8889223
, I need to execute a plugin only for some sub-modules from the parent pom.
For instance to generate the project web site.

I can do this with profiles :

   profiles
   profile
   idsite/id
   modules
   modulemoduleA/module
   modulemoduleB/module
   /modules
   /profile

   profile
   iddefault/id
   activation
   activeByDefaulttrue/activeByDefault
   /activation
   modules
   modulemoduleA/module
   modulemoduleB/module
   modulemoduleC/module
   /modules
   /profile
   /profiles

mvn compile : compile all my three modules
mvn site -Psite : generates the web site only for the modules A and B

That's nice but it could be very interesting to activate my site profile
only when the site is generate. In other word, it would be nice to attach a
profile to a phase. I will have the possibility to do this :

mvn compile : compile all my three modules = activate default profiles
mvn site : generates the web site only for the modules A and B = activate
site profile

This is very useful at least for three reasons :
  - I will not have to explain to all the developers that they now have to
add -Psite ;
  - We won't forget to add -Psite ;
  - I will have the possibility to execute (I hope) : mvn package site.
Interesting with CI like continuum.

We could either activate a profile to a phase if its id has the same name of
the corresponding phase :
   profile
   idsite/id

or with an activation section
   profile
   idmySiteProfile1/id
   activation
   phasesite/phase
   /activation

Hope it's enough clear.

Rémy

Re: Help Me

[Rémy Sanlaville]

It's better to use the maven-user mailing...

I just notice today that If try to use the archetype:create for the first
time, you need to force the update via -U (seems to be a bug...)

mvn archetype:create -DgroupId=testapp -DartifactId=testapp -U


You also have to define your proxy server if needed...

HTH,

Rémy

2006/12/21, Michael Horwitz [EMAIL PROTECTED]:


Hi,

Do you access the internet through a proxy server? If so have you set up
your settings.xml file to operate through the proxy server?

Mike

On 12/21/06, arumahi [EMAIL PROTECTED] wrote:


 Hallo Maven Developers,
 I am new to Maven 2.4.0. I have problem while creating local repositary
 could any one please help me out.when i try to create archetype i have
 error
 saying build error.
 Could any one help me.

 C:\TEMPmvn --version
 Maven version: 2.0.4

 C:\TEMPmvn archetype:create -DgroupId=testapp -DartifactId=testapp
 [INFO] Scanning for projects...
 [INFO] Searching repository for plugin with prefix: 'archetype'.
 [INFO] org.apache.maven.plugins: checking for updates from central
 [WARNING] repository metadata for: 'org.apache.maven.plugins' could not
be
 retri
 eved from repository: central due to an error: Error transferring file
 [INFO] Repository 'central' will be blacklisted
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does
 not
 exi
 st or no valid version could be found
 [INFO]
 
 [INFO] For more information, run Maven with the -e switch
 [INFO]
 
 [INFO] Total time: 21 seconds
 [INFO] Finished at: Thu Dec 21 11:10:49 CET 2006
 [INFO] Final Memory: 1M/2M
 [INFO]
 


 Thank you,

 Aruna.

 --
 View this message in context:
 http://www.nabble.com/Help-Me-tf2864978s177.html#a8006334
 Sent from the Maven Developers mailing list archive at Nabble.com.


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