You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2010/01/01 18:50:05 UTC
Maven 3.0 - Alpha 5 - Maven-BuildNumber-Plugin
Hi there,
i have question about the compatibility of Maven 3.0....
(There is a wiki page about the Maven 3 compatibility)...
I found that the maven-buildnumber-plugin does not work with Maven3....
So what is the best way to document this kind of problem ?
Get an Account on the cwiki.apache.org (if possible) or just report it
via the dev-list ?
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3.0 - Alpha 5 - Maven-BuildNumber-Plugin
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Jason,
>> BTW: Is there a good reason to remove the support of profiles.xml file in Maven 3.0....cause it makes pom.xml a little bit smaller...
>>
>
> It was removed originally to simplify the work in refactoring the way the profiles work.
>
> Then upon looking at any of the projects where I employed this I found that I need many
> separate profile.xml files that it ended up being easier to maintain
> having separate projects.
> Take for example the case where you want to test
> a particular database driver with an ORM.
> The project doesn't scale because has to deal with
> your whole build in order to add support for a driver.
> Whereas encouraging a separate build makes it far more
> modular, self-contained and ultimately easier to manage.
Hm....
>
> I also chatted with Milos and in the cases where you want project
> specific properties we could add some scoping of profile
> application by GA(V) in the settings.xml.
But the problem with settings.xml in my opinion is that it is stored
outside the project folders...(.m2/settings.xml)...
I see the pro about profiles.xml in it's location inside the project it
self (version controled with the project)...
In my case it was simply to control the values of some properties (scm
connection etc. at home and for online...) ...so it was best in
profiles.xml ....so i could simple do mvn -Ponline to active the online
values for the Subversion repository...and in my settings.xml
automatically activated my "homeoffice" profile...without editing my
settings.xml and "poluting" it with project specific information...
It seemed to be a little bit cleaner to put such information into
profiles.xml instead into the pom....but that's my point of view...
> So I would favor scoped profile application from settings.xml
> over profiles.xml files in projects.
>
> It's not impossible to put back, and we might if it causes
> a lot of grief. But I think we added the feature
> originally without much thinking about it.
It does not cause a lot of grief, cause it's simply to solve...just a
little bit discomfort...
Many thanks for the explanation...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3.0 - Alpha 5 - Maven-BuildNumber-Plugin
Posted by Jason van Zyl <ja...@sonatype.com>.
On 2010-01-01, at 2:46 PM, Karl Heinz Marbaise wrote:
> Hi Benjamin,
>
>> What exactly is not working?
> Sorry i missed to attach the output ...
> ...
>
> And after diving deeper into this ...i found it was based on my usage of a project profiles.xml file....unfortunately the support for other profiles than in the settings.xml and pom.xml has been removed for Maven 3.0...(after reading the Compatibility Notes for Maven 3.0 a second time ;-))
>
> After moving the profile into the pom.xml it works fine with Maven 3.0-Alpha-5 ...
>
> BTW: Is there a good reason to remove the support of profiles.xml file in Maven 3.0....cause it makes pom.xml a little bit smaller...
>
It was removed originally to simplify the work in refactoring the way the profiles work.
Then upon looking at any of the projects where I employed this I found that I need many separate profile.xml files that it ended up being easier to maintain having separate projects. Take for example the case where you want to test a particular database driver with an ORM. The project doesn't scale because has to deal with your whole build in order to add support for a driver. Whereas encouraging a separate build makes it far more modular, self-contained and ultimately easier to manage.
I also chatted with Milos and in the cases where you want project specific properties we could add some scoping of profile application by GA(V) in the settings.xml. So I would favor scoped profile application from settings.xml over profiles.xml files in projects.
It's not impossible to put back, and we might if it causes a lot of grief. But I think we added the feature originally without much thinking about it.
>
> The following output:
> C:\ws\supose>c:\prog\apache-maven-3.0-alpha-5\bin\mvn --version
> Apache Maven 3.0-alpha-5 (r883378; 2009-11-23 16:53:41+0100)
> Java version: 1.6.0
> Java home: C:\Programme\Java\jdk1.6.0\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> C:\ws\supose>c:\prog\apache-maven-3.0-alpha-5\bin\mvn clean package
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Subversion Repository Search Engine 0.6.2-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ supose ---
> [INFO]
> [INFO] --- cobertura-maven-plugin:2.3:clean (clean) @ supose ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.0-beta-4:create (default) @ supose ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 2.718s
> [INFO] Finished at: Fri Jan 01 20:22:52 CET 2010
> [INFO] Final Memory: 4M/508M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4:create (default) on project supose: Execution d
> efault of goal org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4:create failed: The scm url does not contain a valid delimiter.
> -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> C:\ws\supose>
>
> Many thanks for the support...
>
>
> Kind regards
> Karl Heinz Marbaise
> --
> SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
> Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
> Hauptstrasse 177 USt.IdNr: DE191347579
> 52146 Würselen http://www.soebes.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3.0 - Alpha 5 - Maven-BuildNumber-Plugin
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Benjamin,
> What exactly is not working?
Sorry i missed to attach the output ...
...
And after diving deeper into this ...i found it was based on my usage of
a project profiles.xml file....unfortunately the support for other
profiles than in the settings.xml and pom.xml has been removed for Maven
3.0...(after reading the Compatibility Notes for Maven 3.0 a second time
;-))
After moving the profile into the pom.xml it works fine with Maven
3.0-Alpha-5 ...
BTW: Is there a good reason to remove the support of profiles.xml file
in Maven 3.0....cause it makes pom.xml a little bit smaller...
The following output:
C:\ws\supose>c:\prog\apache-maven-3.0-alpha-5\bin\mvn --version
Apache Maven 3.0-alpha-5 (r883378; 2009-11-23 16:53:41+0100)
Java version: 1.6.0
Java home: C:\Programme\Java\jdk1.6.0\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
C:\ws\supose>c:\prog\apache-maven-3.0-alpha-5\bin\mvn clean package
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Subversion Repository Search Engine 0.6.2-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ supose ---
[INFO]
[INFO] --- cobertura-maven-plugin:2.3:clean (clean) @ supose ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.0-beta-4:create (default) @ supose ---
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2.718s
[INFO] Finished at: Fri Jan 01 20:22:52 CET 2010
[INFO] Final Memory: 4M/508M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4:create (default)
on project supose: Execution d
efault of goal
org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4:create failed: The
scm url does not contain a valid delimiter.
-> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
C:\ws\supose>
Many thanks for the support...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3.0 - Alpha 5 - Maven-BuildNumber-Plugin
Posted by Benjamin Bentmann <be...@udo.edu>.
Karl Heinz Marbaise wrote:
> I found that the maven-buildnumber-plugin does not work with Maven3....
What exactly is not working?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org