[ANNOUNCE] version.override feature (lightweight maven releases)
Dear Maven users, I improved the version.override feature so that the whole maven build life cycle is now properly supported: With *mvn clean deploy -Dversion.override* a build with an unique version is created without committing anything to your version control or making your workspace dirty. For more information read here: http://diplingfh.blogspot.ch/2013/09/lightweight-release-builds-with-apache.html Best regards, Roger
Obtain a dependency version for output in resource filtering
Folks,
I have a requirement to do the following:
1. grab the version of a particular artifact
2. place that via into a file visible in the final build
I was thinking of using the resources plugin to do this. However, I
can't seem to find the property to reference that points to a version of
a particular dependency.
What I fell back to is the following:
properties
importantArtifactVersion1.2.3/importantArtifactVersion
/properties
depenedencies
dependency
groupIdsome.org/groupId
artifactIdimportantArtifactartifactId
version${importantArtifactVersion/version
/dependency
/dependencies
Then in the file to be filtered:
ImportantArtifact: ${importantArtifactVersion}
This all works fine, and as a bonus makes things easier to update when
versions are bumped.
However, how will this impact the eventual use of the release plugin?
Will the release plugin look at a dependency, find the version is a
property, look for the property and increment that?
If not, what is a good way of meeting this requirement (other than tell
someone to read the POM or site for a particular released version).
. . . still a Maven newbie
/mde/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Obtain a dependency version for output in resource filtering
Hi Mark- I posted the same exact question a few weeks ago and was told
I was being unmaven... :-)
I wrote a plugin to do exactly what you're asking- ill put it on
sourceforge this week.
Sent from my iPad
On Sep 29, 2013, at 2:24 PM, Mark Eggers its_toas...@yahoo.com wrote:
Folks,
I have a requirement to do the following:
1. grab the version of a particular artifact
2. place that via into a file visible in the final build
I was thinking of using the resources plugin to do this. However, I can't
seem to find the property to reference that points to a version of a
particular dependency.
What I fell back to is the following:
properties
importantArtifactVersion1.2.3/importantArtifactVersion
/properties
depenedencies
dependency
groupIdsome.org/groupId
artifactIdimportantArtifactartifactId
version${importantArtifactVersion/version
/dependency
/dependencies
Then in the file to be filtered:
ImportantArtifact: ${importantArtifactVersion}
This all works fine, and as a bonus makes things easier to update when
versions are bumped.
However, how will this impact the eventual use of the release plugin? Will
the release plugin look at a dependency, find the version is a property, look
for the property and increment that?
If not, what is a good way of meeting this requirement (other than tell
someone to read the POM or site for a particular released version).
. . . still a Maven newbie
/mde/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Obtain a dependency version for output in resource filtering
On 9/29/2013 2:26 PM, Richard Sand wrote:
Hi Mark- I posted the same exact question a few weeks ago and was
told I was being unmaven... :-)
I wrote a plugin to do exactly what you're asking- ill put it on
sourceforge this week.
Sent from my iPad
On Sep 29, 2013, at 2:24 PM, Mark Eggers its_toas...@yahoo.com
wrote:
Folks,
I have a requirement to do the following:
1. grab the version of a particular artifact 2. place that via into
a file visible in the final build
I was thinking of using the resources plugin to do this. However, I
can't seem to find the property to reference that points to a
version of a particular dependency.
What I fell back to is the following:
properties
importantArtifactVersion1.2.3/importantArtifactVersion
/properties
depenedencies dependency groupIdsome.org/groupId
artifactIdimportantArtifactartifactId
version${importantArtifactVersion/version /dependency
/dependencies
Then in the file to be filtered:
ImportantArtifact: ${importantArtifactVersion}
This all works fine, and as a bonus makes things easier to update
when versions are bumped.
However, how will this impact the eventual use of the release
plugin? Will the release plugin look at a dependency, find the
version is a property, look for the property and increment that?
If not, what is a good way of meeting this requirement (other than
tell someone to read the POM or site for a particular released
version).
. . . still a Maven newbie
Yep, I agree that it's un-Maven. I'm not happy about the requirement.
However, this is what is currently in use with the ant-based build
scripts. Until I can get a better software release management system in
place, I'll have to live with the requirement.
. . . . just my two cents
/mde/
- sorry about the copious amount of typos in the previous message.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Obtain a dependency version for output in resource filtering
Hi Mark,
Can you explain this requirement a bit more? Where is the version number coming
from, and why? Are you trying to create the file that lists the versions? My
initial reaction is that it sounds like a normal thing to want to do; maybe I'm
missing something.
Regards,
Russ
On Sep 29, 2013, at 2:23 PM, Mark Eggers its_toas...@yahoo.com wrote:
Folks,
I have a requirement to do the following:
1. grab the version of a particular artifact
2. place that via into a file visible in the final build
I was thinking of using the resources plugin to do this. However, I can't
seem to find the property to reference that points to a version of a
particular dependency.
What I fell back to is the following:
properties
importantArtifactVersion1.2.3/importantArtifactVersion
/properties
depenedencies
dependency
groupIdsome.org/groupId
artifactIdimportantArtifactartifactId
version${importantArtifactVersion/version
/dependency
/dependencies
Then in the file to be filtered:
ImportantArtifact: ${importantArtifactVersion}
This all works fine, and as a bonus makes things easier to update when
versions are bumped.
However, how will this impact the eventual use of the release plugin? Will
the release plugin look at a dependency, find the version is a property, look
for the property and increment that?
If not, what is a good way of meeting this requirement (other than tell
someone to read the POM or site for a particular released version).
. . . still a Maven newbie
/mde/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
Come read my webnovel, Take a Lemon http://www.takealemon.com,
and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!
RE: Obtain a dependency version for output in resource filtering
Hi Mark - I've added my artifact properties plugin to sourceforge and
the sonatype snapshot repository.
Project URL: https://sourceforge.net/projects/artifactpropertyplugin/
SVN code: https://svn.code.sf.net/p/artifactpropertyplugin/code/trunk
Snapshot:
https://oss.sonatype.org/content/repositories/snapshots/com/idfconnect/dev
tools/artifact-property-plugin/1.0-SNAPSHOT/artifact-property-plugin-1.0-2
0130930.040133-2.jar
For every resolved compile+runtime dependency, the plug-in will set the
following properties:
- the version of the artifact:
artifact.groupId.artifactId[.classifier].type.version
- the file name of the artifact:
artifact.groupId.artifactId[.classifier].type.filename
These properties are then available for use in other plugins, such as the
Codehaus template plugin, which can insert property values into tokens in
project files.
Let me know if you find it useful...
Best regards,
Richard
-Original Message-
From: Mark Eggers [mailto:its_toas...@yahoo.com]
Sent: Sunday, September 29, 2013 5:55 PM
To: Maven Users List
Subject: Re: Obtain a dependency version for output in resource filtering
On 9/29/2013 2:26 PM, Richard Sand wrote:
Hi Mark- I posted the same exact question a few weeks ago and was told
I was being unmaven... :-)
I wrote a plugin to do exactly what you're asking- ill put it on
sourceforge this week.
Sent from my iPad
On Sep 29, 2013, at 2:24 PM, Mark Eggers its_toas...@yahoo.com
wrote:
Folks,
I have a requirement to do the following:
1. grab the version of a particular artifact 2. place that via into a
file visible in the final build
I was thinking of using the resources plugin to do this. However, I
can't seem to find the property to reference that points to a version
of a particular dependency.
What I fell back to is the following:
properties
importantArtifactVersion1.2.3/importantArtifactVersion
/properties
depenedencies dependency groupIdsome.org/groupId
artifactIdimportantArtifactartifactId
version${importantArtifactVersion/version /dependency
/dependencies
Then in the file to be filtered:
ImportantArtifact: ${importantArtifactVersion}
This all works fine, and as a bonus makes things easier to update
when versions are bumped.
However, how will this impact the eventual use of the release plugin?
Will the release plugin look at a dependency, find the version is a
property, look for the property and increment that?
If not, what is a good way of meeting this requirement (other than
tell someone to read the POM or site for a particular released
version).
. . . still a Maven newbie
Yep, I agree that it's un-Maven. I'm not happy about the requirement.
However, this is what is currently in use with the ant-based build
scripts. Until I can get a better software release management system in
place, I'll have to live with the requirement.
. . . . just my two cents
/mde/
- sorry about the copious amount of typos in the previous message.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Android Maven Plugin 3.7.0 released
The Android Maven Plugin team is pleased to announce the release of version 3.7.0 of the plugin. This is another LARGER release with a lot of NDK related features as well as experimental support for aar package creation. Please take into account that the sdk platform configuration parameter no longer supports platform, only API level works from now on. For NDK users the keyword 'all' is no longer supported for ndk architectures, you have to explicitly list them. Also note that the generated documentation website is now hosted on github http://jayway.github.io/maven-android-plugin/ New features/bug fixes are - Updated builder library version to 0.5.6 - Don't delete nativeArtifactFile if its the same as destFile - Support for maven property maven.test.error.ignore - Use of constant for apk and apklib instead of hardcoded string - Experimental support for consuming and creating aar files - SdkLib? and ApkBuilder? cleanup - Upgraded to builder 0.5.7 and added all dependencies from SDK in version 22.2.0 - Support for multiarch so dependencies and Multiple native architecture support - Adding Native Libs in apk - Make use of aaptExtraArgs in generate-sources goal - Release process changes to use nexus-staging-maven-plugin - Plugin site changed from Google SVN repo to Github pages When upgrading please ensure to check the change log for further details: http://code.google.com/p/maven-android-plugin/wiki/Changelog We would like to thank the contributors to this release for their valuable help and invite you all to help us out as well: Specifically for this release we would like to thank the following contributors for their awesome work. - Benoit Billington https://github.com/Shusshu - Mark Riley http://markriley.net - Stéphane Nicolas https://github.com/stephanenicolas - Joonas Javanainen http://gekkio.fi/ - Johan Lindquist https://github.com/johanlindquist - Charles Harley - Tadeas Kriz https://github.com/TadeasKriz - Manfred Moser http://www.simpligility.com Documentation, issue tracker and more can be found on the plugin website at http://code.google.com/p/maven-android-plugin/ For a primer to use the plugin check out the Android Development chapter in Maven: The Complete Reference http://www.sonatype.com/books/mvnref-book/reference/android-dev.html Please join the Maven Android Mailing List for relevant discussions: https://groups.google.com/forum/?fromgroups#!forum/maven-android-developers Enjoy Manfred Moser http://www.simpligility.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
